Applying Host Profile vCenter Appliance 5.1 vSwitch Route based on IP hash

I am upgrading my environment to 5.1 from 5.0 and have decieded to go the "clean install" route for practice and experience. I have a small environment with only three hosts. I have run into an issue where a host profile taken from my first host has failed to fully apply the profile to my second host. After some trouble shooting, I figured out that it was failing because the NFS datastores that it should have been mounting during the applying of the profie was failing. The reason the NFS was failing to mount was because the vSwitch that connects to my NFS VLAN is using LACP and needs to be set to "Route based on IP hash" in order to communicate. vCenter had created all four of my vSwitches perfectly with the exception of my only vSwitch that needs to have the load balancing option set to "Route based on IP hash" rather than the default "Route based on the originating virtual port ID" Once I manually modified the vSwitch and then applied the profile everything went perfectly.

So my question to you all is this: Is this an expected behavior, or is it an oversite by VMware that vCenter is not capturing the "Route based on IP hash" setting from the "gold" host and then applying that setting to other hosts?

Quick details on steps taken.

1. New ESXi host1 with clean install of 5.1 from ISO
2. Configured host1 exactly the way it needed to be
3. Imported and configured vCenter Server Appliance from OVA
4. Clean install of host2 from ISO with only management network configured
5. Created profile from host1
6. Applied profile to host2
7. Failed
8. Changed vSwitch on host2 that was created in step 6 to "Route based on IP hash"
9. Applied profled to host2
10. Success!