, interesting question - I am not aware of any pertinent variance in the backend settings applied to node for each cluster type that would cause any difference here.
If you have this already configured as stretched, you should be able to easily check this by creating the policy that would store data like this and validate whether it shows the vsanDatastore for this cluster as compatible (and if it does then validate by creating a test VM with this policy):