This doesn't really make sense.
If you want to load test the VM with a given virtual hardware configuration, the host must be able to provide it consistently and reliably; if there is resource contention on the host, the VM will slow down (along with all the other VMs running on the same host) and the load testing results will be meaningless.
You can limit the resource usage of a VM, but if you do that the VM will behave as if it has fewer resources available; you will save the other VMs from slowing down, but the load testing results will be just as unreliable (if not worse).
Update:
According to your comments, you want the VM to run at full performance regardless of the load on the host, even if this means slowing down other VMs.
This can be done to using reservations for CPU and RAM; this also applies to network bandwidth.
For disk I/O things get a bit more complex because you can only define relative priorities between VMs, but you can do something similar using disk shares.