I'm old school IT so I played with NTFS for several years on servers etc.
Since I formatted all of my cards exFAT32 (32gb and 64gb) are you saying the aircraft won't recognize the 32's with exFAT32?
I go back that far too, even further back with Novell 2.0
Anyway, the FAT (File Allocation Table) in FAT32 only has so many clusters it can handle. The cluster size range Windows will allow won't get you past 32GB. Even using Format in a command prompt will give you an error if you try a cluster size giving you more than 32GB. There are third party tools to force it, but DJI likely will not accept it.
FAT based formats with older OSs used to be notorious for corruption, particularly if a write cycle was interrupted. A cluster may be allocated to data but the chain not linked to a file entry in the directory. But it is common across most OSs, not proprietary so it's widely used, particularly among "things". I haven't seen corruption in years, not that I've run chksk against them in years.
I'm not sure about using ExFAT for smaller storage. You might be eating up more of the storage for FAT than you actually need which would be inefficient.
Some systems may be OK with it, others may reject the deviation.
Other file system formats act like a database with transaction logs/journal recording changes. NTFS is one of them. The logs get written first and quickly before the master tables get updated. If an inconsistency is detected, the transaction log can be used to apply lost changes, or role back a corrupted change. Journal based file formats are usually specific to a particular OS.