Migrate vCenter server back to machines hosts using vDS

I have an interesting delimna.  I have a test environment with two servers running 5.5, both hosts are configured with virtual distributed switch (vDS), call this TESTEnvironment1.  The vCenter VM these host servers are joined is hosted on another VM host and part of another test vCenter, call this TESTEnvironment2.   For consistency, I prefer to have the vCenter server for TESTEnvironment1 migrated back to its two VM hosts.  Both TEST environments see the same shared storage.  When I power down the TESTEnvironment1 vCenter hosting TESTEnvironment1 hosts, remove from inventory on TESTEnvironment2.  When I add vCenter server for TESTEnvironment1 comes up, it can't get an IP address since vCenter isn't online to distributed addresses / ports from the vDS.  And I can't manage the vCenter for TESTEnvironment1 since it uses the web client.   Both vCenters are windows based.

So...I added a third VM host to TestEnvironment1, made the networking on the third host use a standard switch and attempt to add the vCenter server for TESTEnvironment1, the server is added fine, the networking portion on the VM is stable, but can't ping out.

Can i have two clusters in the same datacenter, one cluster with two hosts using vDS and a single host using a standard switch?

These environments were from a previous technician who left and I'm trying to retain TestEnvironment1 and eventually retire TestEnvironment2.  vDS requires vCenter to be online and web client available.  When it's offline, I'm dead in the water and can't use the full client since they are version 10.   From what I read, the workaround right now is have your vCenter server hosted on a machine with a standard switch while GUEST hosts use vDS.  I only have one vLAN for both management, vmotion and guests to keep it simple.

For summary

TESTEnvironment1

host1 - uses vDS

host2 - uses vDS

host3 - uses standard switch

TESTEnvironment2

host1 - uses standard switch

vCenter - for TESTEnvironment1 (I want to migrate to be hosted on one of the servers in TESTEnvironment1)

vCenter - for TESTEnvironment2

          Hope this makes sense.