As of MC17, one such problem has an implemented workaround:
http://yabb.jriver.com/interact/index.php?topic=66413.0but this won't help users of previous versions of MC.
There can be other problems. Consider an MC1 user updating some property and having MC1 update tags, for all 10,000 of your files. This will take a little time for the updates to reach the files, it happens in the background.
Now, a second MC2 makes some tag changes on the same files that MC1 made changes for. Some of those MC1 files may have been updated; some may not yet have been updated. MC2 writes the tags, updating the file.
What does MC1's background tag writing do? Overwrite MC2's changes? Skip MC1's changes?
This is called a Race Condition, and it is always possible to occur when two competing systems are not synchronized using effective locking mechanisms. And MC was not designed in this usage model to guarantee atomicity in this case.