You can configure a Vagrant box how ever you see fit - install everything and anything on it and then spread it among other devs so everyone has an identical environment. Configure it to match 100% of your production server, and you have even more parity - instant cloned production environment inside the company, but ready for development and experimentation. Screwed up? Just vagrant destroy and vagrant up a new instance, you’re back where you started with zero code lost, only a reset environment.
Also SSHing into your environment still won’t reveal you running Vagrant. He’d have to get sudo privileges of your computer and scan the process list that way, which, if it’s done regularly, is not only detrimental to morale and productivity, but also to your station’s performance. Seems like a draconian workplace in any case. The only inspection a dev should be subject to is code review.