Still ZFS for stability ?? Pull the power plug while writing and you know what your stability is worth in reality. I would say say ZFS is for verify as long as you have a usv in front of your server otherwise with a poweroutage you should have a good backup and be able to do a full restore.
That's true, only mkfs.xfs & mount is required, any tuning options are optional. Write to filesystem while cut host power, last written data is incomplete but filesystem is coming up. With zfs you will get good chance for loosing import pool and all created datasets and even all snapshots at once in that case, so send/receive server should have other power, usv is good for clean shutdown and even backup always good to know :-)
Anytime the day will come where zpool options clear, -f, readonly, -F, -X, -T in any combination wouldn't help importing a pool. The best is to check that out by yourself by a power cut while writing to a testpool dataset and just be prepared for such a case. Theory and reality are two storys and not equal be design.
Yes, without the auto-survive of a power outage zfs will never be accepted by redhat whatever the zfs license is look like in the future, still this simplest thing can bring lots of headache and pain even zfs designed zil and slog but what it's good for when you google cannot import pool ... ?!
These features keeps me solidly without ZFS:
0. Powercut zfs host : cannot import pool without destroy old and create new.
1. For case "0" need minimum 2nd zfs host while backup restore even slower.
2. Extrem slow meta-/data reads with aging, eg try tar any dir to /dev/null.
3. So stay working with other alternatives and have fun.