In theory VT-d could provide much better support for emulation and handling of hardware devices within a VM and, for example, take some of the grunt work out of moving data from the VM network interface to the host network interface.
In all honesty for home users you're probably not going to see a massive boost to your VM performance with VT-d, it looks to me more geared around multiple heavily used concurrent VMs, but there may be a bit more performance if your VM host software supports it.
See:
Understanding VT-d: Intel Virtualization Technology for Directed I/O
Intel® Virtualization Technology for Directed I/O
Intel® Virtualization Technology (Intel® VT) for Directed I/O (Intel® VT-d) Architecture Specification
Looking at that last document (section 2.5 if you're interested) VT-d's main features appear to be allowing more separation of I/O to devices from VMs (so that each VM can effectively have it's own buffer to a device) and allowing VMs with appropriate drivers to have nearly direct access to the host hardware while still remaining protected and secure.