That problem is solved by having backups. ZFS dis not a replacement for backups.
Oh, and there's always zdb, the ZFS debugger, you can use it to walk the on-disk structures.
Also, is "you can't rely on fsck to alleviate that problem" an argument for not having an fsck?
Is there a particular type of data corruption that fsck would recover that ZFS would not?
If your OS or disks are buggy, you are hosed, anyway, as that checking tool would run on the same OS and hardware.
You should look at ZFS as having a built-in fsck that is automatically invoked when needed.
I'm not too familiar with exactly how fsck works, but it seems to mainly stitch bad metadata back together so there's still no guarantee that your data is perfectly restored. This would be especially true if a bad FS write operation caused the data to be corrupt.
If the data is really corrupt the FS doesn't have any inherent way of knowing what the correct data should be.
If you are happy that the ZFS code is perfect, then it makes sense to rely upon its consistency checks, snapshot features, etc (and I'm not criticising those). But what if ZFS isn't 100%? How do you recover your data?