FUSE one is not just read-only. It had capacity to do write on NTFS partitiona for decade at least.
But, it is FUSE.
Am I correct in saying that there shouldn’t be any reason that being FUSE would in and of itself cause corruption?
Performance is a different question, since it’s not in kernel.
Off the top of my head... ordering violations. FUSE has a lot less control about the exact order in which things get written to disk, meaning that you are more likely to wind up with the wrong parts having committed down first if there's a crash.
That’s FUSE which is in userspace. The kernel driver is read-only. I believe it never progressed past that due to licensing issues.
I know what FUSE driver is, but my educated guess would be that almost no one ever used in-tree kernel-space driver which you referring to. So when people talking about issues with old driver that's almost certainly NTFS-3g