Hello smittytech,
While you can add an existing vSAN cluster to a new/different vCenter, I would generally not advise starting from scratch and instead figure out why the vCenter VM is having issues.
In most cases vCenter has too much SEAT data and configurations to simply be discarded (but then again anyone that values it has current backups of it), if this is just a home-lab and/or you don't care about vCenters data then by all means make a new one, but otherwise please contact support to get the original one functional.
If you don't have a support contract and want to troubleshoot it yourself I would advise starting with validating that the VM is not registered/running on other hosts (and thus getting marked as invalid when attempting to run it on current host) - is it getting marked as invalid on registration or on power-on attempt? If the latter then check the vmware.log that should have been generated for the reason (e.g. can't create vswp, missing vmdk etc.).
Bob
