Having four 10G interfaces gives you some flexibility. I'm assuming these aren't Cisco VIC cards or the broadcom cards that can create virtual partitions.
There is a section at the bottom of this cisco document that goes through some teaming options for the vSphere Standard Switch. May be a useful read, these are based around two 10G but should give you some ideas.
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-1000v-switch-vmware-vsphere/white_paper_c07-607716.html#_Toc265279882<https://urldefense.proofpoint.com/v1/url?u=http://www.cisco.com/c/en/us/products/collateral/switches/nexus-1000v-switch-vmware-vsphere/white_paper_c07-607716.html%23_Toc265279882&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=FGyPC8ZSvBkKihkoeKgCmjuZI2qYJ8xvSchS1aM1v%2Fc%3D%0A&m=sv61%2B8LA4EkdU%2BJ912tFSAWgDh98jZFX9qSB64AyAWs%3D%0A&s=d357d9b968a896f3af9a2f80b29c49fb9987f6e2541de22c347174ac8458901d>
Your VLANs and IPs look fine. Your vMotion and SAN storage VLANs probably don't even have to be routable, you just need a L2 VLAL created on the upstream switch.
I would carve this up with two vSwitch instances, then manipulate the failover order for each vmKernel interface or port group.
MGMT (VLAN100) - vSwitch0 - Active vmnic0, standby vmnic1
vMotion (VLAN200) - vSwitch0 - Active vmnic0, standby vmnic1
Storage (VLAN300) - vSwitch0 - Active vmnic1, standby vmnic0
VMTraffic (VLAN400) - vSwitch1 - Active vmnic2, Active vmnic3
As you create new VM port groups on vSwitch1 they won't require editing, the defaults should be route based on port ID with both nics active. This will pin your VMs to on or the other active adapters based on port ID.