@JoeMontana, while it likely is a case that it is possible to change the name (e.g. there is probably no guardrail preventing this and vsanDatastores are re-nameable entities), it may break things in VCF inventory (as VCF didn't assign the new name you assign), from VCF Communities where this was asked previously indicates this also https://communities.vmware.com/t5/VMware-Cloud-Foundation/Renaming-VDS-and-VSAN-Datastore-process/td...
As there is no documentation referenced in the above and as I cannot find anywhere where this is clearly documented, I would advise asking someone from VMware VCF GSS team or DEMC VxRail support.
Looks like there were some enhancements to what can have name changed after creation in VCF 4.1 but I don't see datastores listed as one of the entities there:
https://infohub.delltechnologies.com/p/take-vmware-tanzu-to-the-cloud-edge-with-dell-technologies-cl...
Support for Renaming VMware Cloud Foundation Objects: You can rename workload domains, network pools, and compute clusters after you have deployed them. This allows the flexibility of naming these Cloud Foundation objects to align with company policies
https://docs.vmware.com/en/VMware-Cloud-Foundation/4.1/rn/VMware-Cloud-Foundation-41-Release-Notes.h...