Hey,
It would great to hear what exactly you are trying to accomplish.
As for your questions.
Hyper-V replication is used to replicate VMs from primary host on schedule. It doesn't support automatic failover, you can trigger it manually. https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/set-up-hyper-v-replica
Storage replica is used to replicate Volumes between servers or clusters. It is a DR solution like Hyper-V replica. The main difference that SR allows you to replicate entire volumes with multiple VMs. In addition, it can be used to created stretched cluster. https://learn.microsoft.com/en-us/windows-server/storage/storage-replica/storage-replica-overview
S2D - can be used in Failover Cluster. It is used as a shared storage for Failover Cluster. It support different protection levels across the cluster nodes (mirror, striped mirror, parity or dual parity). https://learn.microsoft.com/en-us/azure-stack/hci/concepts/storage-spaces-direct-overview
SAN can also be used as a storage for Failover Cluster. You can still use NTFS as a ReFS alternative.
As for encryption, bitlocker can be used with Cluster Shared Volumes. https://learn.microsoft.com/en-us/windows-server/failover-clustering/bitlocker-on-csv-in-ws-2022
In addition, StarWind Virtual SAN can be used to replicate storage between nodes and provide it as a shared storage to Failover Cluster. Check for more info: https://www.starwindsoftware.com/starwind-virtual-san
Cheers,
Alex Bykovskyi
StarWind Software
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.