I've had local storage in Hyper-v cluster and moved stuff to it and back. Also this move VMs to local storage and back for SAN reboot sounds silly. SAN should have dual controller so VMs should be fine during SAN reboots.
My experience with vSAN vs S2D is what sets the MS solution ahead. It would take 24 hours for me to put a host in maintenance mode in Vmware. Even SSD storage needed SSD cache. MS seems smarter and more flexible and has more tools to see what is going on. I haven't used vSAN in a while but I haven't heard anyone really talking it up and using it in production either.
To be honest, nobody other than those willing to ride the edge, are willing to talk up either S2D or vSAN. I've deployed both and from my experience they both have their niches but for on-prem deployments, a lot of admins, particularly storage admins hate the idea of vSAN and S2D. That's even with ready nodes, they just don't trust it. I've had less experience with Nutanix, but they're also a leader but still not widely adopted. I've had some experience, was impressed...that being said, for those that want to walk the SDS/HCI space, vSAN and S2D seem to be the two most common that I've worked with. Even so, most clients go with more traditional SAN products. It's hard to sell someone on new solutions when they've run their past Hitachi into the ground with almost nothing to be heard of in terms of unplanned downtime and pages upon pages of easily found disappointment with S2D and vSAN.
It's for these reasons that my on-prem work is a fraction of my cloud work now. Things are changing fast, faster than I ever thought it would and a lot of it has to do with the real disappointment and unrealized ROI that the aforementioned solutions typically present and the astronomical prices of more reliable, more traditional, on-premise solutions.