Hi Guys thank you for your replies. I'd setup the Tags, storage policies and such in the recommended order but I do appreciate the clearing up that you don't need to take the datastore clusters just the datastores and also thank you for clarifying there is no further use of the C# client's storage profile area. I'd tried the resetting and reconnecting as recommended in other posts but no solution presented itself.
I did fix the problem though! (I think!)
I am running things out of recommended spec and I realized this might have caused the issue and confirmed things are working now: I am running the vShield Manager as an appliance on the same host pool as the vcloud's intended Provider VDC. When I was adding the Provider VDC I was shutting that appliance down prior to getting the hosts reconfigured (otherwise it was blocking the host it was on from upgrading) and that is likely what the problem was. This time I made sure vMotion was available and shifted the appliance to a host that finished the addin process before its first home's upgrade attempt's timer had run out. Now all the hosts are properly incorporated into the director while the vshield manager remained online.
When I add a new tag & storage profile (and tag a datastore, won't show up otherwise) it shows up as an option! I'll report back though if I'm just preemptively calling this situation fixed.