I can provide you with some information. This is what I read on page 27 of documentation in Trend's installation guide regarding the naming: http://docs.trendmicro.com/all/ent/ds/v9.6/en-us/Deep_Security_96_Install_Guide_vmsafe_EN.pdf
"The names of drivers differ according to the ESXi version. If the ESXi version is ealrier than 5.5 u2, the driver is named "vShield Endpoint Thin Agent". If the ESXi version is 5.5 u2 or later, it is named "Guest Introspection Thin Agent". For version 6.0 Patch 1 (ESXi-6.0.0-20150704001-standard) or later, the name of the driver is "NSX File Introspection Driver". Please note that the name of the driver may be changed without notice."
As for NSX and use of vShield, this is what I received from a Trend engineer prior to my deployment (Please note that I do not use NSX, I have vShield deployed for now)
Please have the following downloaded & prepared prior to the Deep Security implementation.
• ESX(i) / vCenter 5.x, 6.0
• A Windows server available for Deep Security (optionally a Linux server may be used)
• If NSX is configured for the ESX environment, then skip the vShield manager requirement.
• vShield Manager 5.5.4.1 - obtained from Vmware -included in vCloud Networking and Security Bundle.
• vShield Endpoint (EPSec driver) - part of the Vmtools package
• SQL (from Microsoft) or Oracle DB
NOTE: SQL Express should only be used for a test environment or a very small, limited deployment environment
• Two static IP addresses (for vShield Manager, Deep Security Manager)
• Additional static IP addresses (for each Virtual Appliance to be installed on each ESX host)
Edit:
Forgot a link: VMware KB: Implementation of VMware vShield Endpoint beyond vCloud Networking and Security End of Availability (EOA)
Please see the final question on the Q&A. It may help as well.