Could you tell us some more about your usecase so we can take this into consideration for future releases / licensing?
Don't know where these quotes came from and I don't get them... but anyway a Standard vSwitch works fine with auto-deploy. Auto-Deploy relies on host profiles to configure the ESXi hosts. So all settings you would normally set locally will be done via a host profile.
This isn't true. Resource pools can *still* be configured at the host level. My understanding is that in vSphere 4, if you created host-based resource pools, their configuration was stored only on the host. In vSphere 5, the resource pool definition will be stored in the vCenter Server DB, but each host will still store the config too, just as standard switch definitions are pushed to the host. Hosts must still be able to boot independently if the vCenter Server is unavailable, so these settings will be pushed to and stored locally on the hosts in vSphere 5. And for auto-deployed hosts, the info needs to be stored in the vCenter Server DB, so that the host can be delivered its config on each reboot. So my understanding is that both host-based and cluster-based resource pools still exist in 5.0.