Actually ran into this while doing some experiments with ZFS & Postgres, some non-enterprise drives will pretend they wrote data when they didn’t and you can corrupt a even a rock-steady database like Postgres.
If you’re not afraid to lose some perf, you can disable volatile write cache on your non enterprise drive:
https://vadosware.io/post/everything-ive-seen-on-optimizing-...
I've actually had the opposite, I want ZFS to ignore the massive amount of fsync calls things like chromium or regular desktop applications make (without becoming generally unsafe). I've resorted to preloading libeatmydata instead. The disks are PLP and the machine is behind an UPS, things shouldn't/don't have to hit the disk all the time.
Not recommended, but this is one of the things I tried (I tuned it to 1s to be slightly safer):
https://vadosware.io/post/everything-ive-seen-on-optimizing-...
But you probably want to be very sure that your desktop applications are somewhat safe with their data/can recover from crashes...
TIL of libeatmydata[0], if you're comfortable using that, you'd probably be comfortable disabling fsync on the datasets for those apps.