You can host plugins on another directory/drive/partition using filesystem junctions/links.
Are you on Windows or Mac?
I’m not sure what’d be best on Macs (symbolic or hard link?). On Mac it’d done through a command line with the ln utility (ln for hard link, or ln -s for symbolic). My best guess would be to go with the ln -s option, and only link entire directories.
With Windows, VST3 plugins are kept in: %SYSTEMDRIVE%\Program Files\Common Files\VST3
Using a command line in admin mode, you can use mklink to create filesystem junction from a directory on the system drive to some other location. You could move the entire VST3 directory, or you could have a subdirectory that points elsewhere, and thusly keep some plugins on the system drive, and other plugins elsewhere.
I.E. Say you have a secondary drive of which you’d like to move some plugins to the directory:
D:\VST3overflow
You could establish a junction to this location like so:
mklink /J "%SYSTEMDRIVE%\Program Files\Common Files\VST3\VST3overflow" "D:\VST3overflow"
At that point you’ll find a new directory on your C drive
%SYSTEMDRIVE%\Program Files\Common Files\VST3\VST3overflow
that points to the contents of D:\VSToverflow
Since VST3 hosts are supposed to also check any children directories of “%SYSTEMDRIVE%\Program Files\Common Files\VST3”, any plugins you move there should continue to work.
Alternatively, you could cut and paste the entire
%SYSTEMDRIVE%\Program Files\Common Files\VST3" directory to a different drive, then make a link to the new location.
mklink /J "%SYSTEMDRIVE%\Program Files\Common Files\VST3" "D:\VST3"
NTFS Hard Links, Junctions & Symbolic Links Explained (2025)
Using such links, you can even maintain completely different sets of plugins in different locations, and easily swap among them by simply changing the filesystem link.