For info on my side, now that kernel 5.15.2 has landed on Testing branch with support for ntfs3, I changed my previous fstab for new ntfs3 type, and it works as intended so far.
Before (just an example for the NTFS partition part):
UUID=A1B2C3E4F5G6H7 /path/to/mount1 ntfs-3g defaults,big_writes,windows_names 0 0
UUID=7H6G5F4E3C2B1A /path/to/mount2 ntfs-3g defaults,big_writes,windows_names,noauto 0 0
Now
UUID=A1B2C3E4F5G6H7 /path/to/mount1 ntfs3 defaults,noatime,uid=omano,gid=omano 0 0
UUID=7H6G5F4E3C2B1A /path/to/mount2 ntfs3 defaults,noatime,uid=omano,gid=omano,noauto 0 0
Fore reference, as usual, the documentation linux-ntfs3/ntfs3.rst at master · Paragon-Software-Group/linux-ntfs3 · GitHub
ntfs3 support all the standard options, and the ones listed in documentation (for instance it wouldn’t mount with big_writes and windows_names options).
I had to specify the uid and gid or else I wouldn’t own the partitions and content. Before I just needed to own the mount point with ntfs-3g. Maybe there is a better way but I didn’t find issue so far doing so.