I use a pointer file to load v through registry (using apppath and a fake name). When the apppath is loaded, it loads the correct version of v. Part of the installation is to reactivate v after a tcmd update.
The pointer file is a copy of write.exe, called v.exe, modified to load some name like zviewer.exe, A backup of v.exe is held.
The apppath for zviewer.exe points to where-ever v.exe is installed.
The v application can be kept off path, while a copy of v is kept in the tcmd directory, and in some pathed directory. You can then start v from either location, either under tcmd or via a cmd prompt.
The same issue exists with everything. The WSCC program looks after the Sysintern utilities, the Nirsoft utilities and a few others. While it is designed to be portable, you can redirect various shortcuts and links through these utilities. WSCC also looks after everything, so i simply run it from there.