My preference is always to seperate the management traffice form VM traffic and this also VMware Best Practice - so I would have one vSwitch with the vmkernel and vmotion port- this way if the VMnetwork becomes saturated you will have a better chance of connecting to manage the hosts
In terms of NIC teaming policy it really will depend - the simplest is the Route Based on VIrtual Port ID - distrbutes the traffic across the physical NICs and will not require any modification to your physical switches. Route Based on IP Hash will add an extra load to the ESXi host since every packet is examined but the benefit gained is the traffic of VM will be moving across multiple NICs only if the VM is talking to multiple targets with different IP address. You will also need to configure your physical Switch envionment for LACP/EtherChannel -