Consolidation of vsts

Yes, it's the way to go. One for x86 VSTs and one for x64. Install everything into those two, and you'll never have to go looing for things again.

I have a folder for 32-bit and 64-bit VSTs. I have a few VST3 devices, but I don't use them.
Under these folders are only Manufacturer names and the vendor products go in that folder.
 
I've found that one can usually manually move the DLLs and sometimes it necessary.
 
For example, one VST I have puts it's 64 and 32 bit DLLs in a single folder. So I move them.
Other times when you install, the path isn't quite right because the vendor adds their name to the folder without telling you - so you create a Vendor X folder and the stuff gets installed in folder X/X/ under the VST folder - so I move these up a level and delete the duplicate folder.
 
After I install one, I usually put all documentation in a global folder and place a shortcut from the docs to the VST path.
 
For really complex installations, the VST data such as tunings, presets, etc., is saved elsewhere, such as AppData/Local, AppData/Global, ProgramData, or whatever. For these types, I make shortcut pointers to all these locations in the VST folder for future reference. I will probably forget about these things later on.
 
Finally, I put the license keys and URL shortcuts to the manufacturer site in the VST folders.
 
This can take a bit of time when I install the thing, but I only need to do it once.
 
After all this, I usually check the registry data to make sure any stored paths for the VST are still valid after the move.
 
After all this, and only after that, I run the VST for the first time, license it, etc., so the paths are checked on the first-run.
 
I usually use a simple DAW like SaviHost as my first-run application. That way I avoid messing up my main DAW if I need to adjust things.