It's possible during setup though I'm not sure how supported it is. Not sure why you'd really want to, writes are much slower than NTFS in general due to journaling.
For the same reason I want btrfs or ZFS on Linux; cheap snapshots so if something breaks I can easily restore to a safe point.
A large part of my complaints about Windows Update have come because it can brick your machine, System Restore doesn’t work, and so you’re stuck spending a weekend trying to back up and fix stuff.
When I ran Ubuntu with ZFS on root, I had it so that I every time apt was run, it took a snapshot. This came in handy when my WiFi driver got borked during an update; I was able to restore from a previous point, it took like ten minutes.
ReFS doesn't give you any more rollback capability than NTFS in that sense. ReFS supports file level snapshots, not volume.
And on a client machine, it's of much less importance overall (to you, it may be super important and I don't want to discount that). And on the server side, that's why we have n+2 failovers. No single machine of importance should ever be a point of failure... I realize that's not always reality but it's more or less Microsoft's position; after all, why sell one Windows Server license when you can sell 3!
NTFS getting corrupted by the tiniest errors would be one reason to use ReFS
Using it for the OS partition is not very well supported right now though (for a consumer), installing etc. works fine, but DISM doesn't support ReFS so adding features generally doesn't work
Can't recall the last time I saw a corrupt NTFS volume... even when using Storage Spaces. I'm sure it's happened to someone given Windows is in use by billions of machines, but NTFS becoming corrupt can't be all that common.
Besides, ReFS doesn't do data journaling by default.