Response from Freefilesync developer.
I read through the Microsoft docs you posted earlier and others, and I agree with the Freefilesync developer.
It appears the best way to track all files on a volume on NTFS is to use fileid which is expected to stay persistent. This requires no extra overhead or work as the Filesystem maintains FileID’s automatically.
ObjectID requires extra overhead and is only really intended to track special files like shortcuts for link tracking etc.
Any software that is emulating an NTFS system should therefore provide FileID’s and guarantee they stay persistent with a file on that volume.
I am seeing the direct performance impact from this and agree with Mitch that there can be other adverse side affects potentially much worse than just performance issues if someone uses software that expects FileID’s to behave as per Microsoft’s documentation.
Finally also note that ObjectID is not supported by the Refs filesystem, whereas FileID is.
https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/ntifs/ns-ntifs-_file_objectid_information
ReFS doesn't support object IDs. ReFS uses 128-bit file IDs, so can't cleanly distinguish between file ID versus object ID when processing an open by ID.