Ah yes, I had almost forgotten about that. It is indeed worth pointing out to anyone not familiar with NTFS-3G.
For anyone not familiar with the lingo in the aforementioned knowledge base article, basically if Windows crashes (or is improperly shutdown) it doesn't leave an "all clear" signal on the hard drive. When Windows doesn't see the "all clear" Windows knows that it crashed and that the disks need to be checked to make sure nothing is wrong.
In Windows a disk check is merely a suggestion (one you should probably follow), but NTFS-3G makes disk checks mandatory. It is a safety precaution if I understand it correctly, and can be easily addressed by running a check-disk in Windows. Or, if you're the person who likes to throw caution to the wind, I believe you can disable the mandatory disk checks in NTFS-3G.
Either way, It's not a huge issue to me personally. Others may find that such behavior is too much to live with and then they can decide for themselves. Good to have information one way or the other.
The only other problem that I can see on a cursory glance through the knowledge base is
KB4756 . KB4756 says that "Parallels Desktop SmartSelect won't open Windows files in Mac OS applications" with NTFS-3G installed. This apparently applied to parallels 3.0 (and was supposed to be addressed) and MacFUSE 0.4 . The issue appears to still be present in Parallels 4.0 and MacFUSE 2.0.
Basically what this means is that if you try to execute "windows_program.exe" on an NTFS volume from Finder nothing will happen. Doing the same thing from a mac volume (even with NTFS-3G/MacFUSE installed) runs the program in Windows.
Again, if this is a deal-breaker for you, then uninstall NTFS-3G. Personally I don't run that many programs from NTFS volumes, and those that I do I can still execute by browsing to the disk in Windows Explorer rather than in Finder.