Ladies and Gentlemen,
so we've build another test setup: "shared nothing" Hyper-V cluster with a guest VM cluster inside (both VMs run on a different nodes). See:

So **UNFORTUNATELY** this setup seems to be broken so far and we cannot figure out why exactly: is it our or MSFT "flaw by design" issue in Windows 10. For the whole story you may look @ this blog with a "cooking book", see:
Storage Replica: Hyper-V Cluster, Guest VM Cluster, Shared VHDX, 2 node, no shared storage, NO GO :(((
http://www.starwindsoftware.com/blog/storage-replica-with-microsoft-failover-cluster-and-guest-vm-cluster-role-windows-server-technical-preview/
Hope to get another build, some feedback from MSFT why we should not be doing this or what we did wrong and try again :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.