The underlying problem is that Time Machine stores a disk image over the network[0]. If the disk image is not unmounted cleanly, Time Machine treats it as horribly corrupted and refuses to touch it. And this happens very often if you're using a laptop that will be unexpectedly disconnected from its storage constantly.
[0] This is to support things like hardlinks, etc. Ironically this is to emulate what BTRFS snapshots do natively. No clue if modern Time Machine uses APFS, but so long as they shove the actual data inside of a disk image this problem will continue occurring.
This is true. Though I've had very good luck re: ZFS and my current Samba config.
If you're not already, you should be snapshotting before and after each network mount. See: https://kimono-koans.github.io/opinionated-guide/#on-network...
I came here to see if someone had built a macos native time machine, but this looks like just another hack.
I do wish Apple would allow 3rd party applications to populate "versions", so the inbuilt UI could be used with other apps. It could even fit with their existing Finder extensions: it could bring together different versions of a file on cloud providers, local backups, etc., and present them in a unified UI.