Mac classic resource forks, while most user friendly, were maximally power user opaque. OS X resource forks implemented as files create underlying file system messiness on non macs across network file systems but at least solved the migration and backup problem in a UNIX-like way. A slight tradeoff that's a win for interoperability.
Windows NTFS ADS, allowing any file to contain any number of other files hidden to the user was a terrible idea that never should've happened. It still works in Windows 11 and it's a giant security vulnerability that marches on because of the tyranny of "compatibility".
File metadata should be possible but it should be limited to essential OS housekeeping activities but definitely not by applications.
Faithful backup, restoration, migration, and archival needs keen attention to the preservation of platform-specific filesystem metadata and maintaining the faithful integrity of such.