If you use ZFS, you probably are on FreeBSD. Then you would not see the advocacy of systemd that sometimes borders on insane, as a problem.
Its kind of like upgrading an outdoor carpentry project, like a deck, from nails to deck screws, then just in case you miss the feeling of hitting your thumb with a hammer, someone helpfully finds a link to install deck screws using a hammer. That's impressive in its own way, but ... I think I'll continue moving everything to Freebsd instead.
for you to suggest "not getting yourself in this situation in the first place", well, that's exactly the bullshit behaviour that i think most of us find utterly abhorrent.
Strictly speaking ext4 doesn't require it either, it's just highly recommended that there be a periodic e2fsck -f (i.e. check even if the journal is consistent and says the file system is clean), by default this is 180 days but the user can modify or disable this with tune2fs. It's possible to make it mount-count or time-dependent. See tune2fs -i.
Systemd people are not helping the community.
Also: https://rudd-o.com/linux-and-free-software/ways-in-which-zfs...
I use ZFS, which does this sort of thing in the background while the system is live. In fact, every read from a ZFS filesystem does a complete integrity check of everything that read depends on. If it finds an error during that process it fixes it before returning data to the caller, or returns a read error if it cannot. Those errors get collected and logged, so that if they do occur (usually due to faulty hardware) you can recover the effected files from backup.
This is much better than a surprise fsck when you're running late.