It depends if the plugin is portable or not. To be portable it requires that it doesn't write to any hardcoded paths or registry, at least not essential things it cannot 'regenerate' if they don't exist. If it does write to the registry but it can work without having them pre-generated (by installer etc), then it's said the application is portable but not stealth. Easiest way to check if a VST is portable or not is to install it in a Sandbox or Virtual Machine first (sandbox is far easier / less hassle) and then inspect the registry and/or files it created. Or just copy the .dll/vst3 after installing in sandbox and see if it runs outside of the sandbox without the registry or hardcoded files. But tbh this is one of the reasons, apart from bloat, of why I hate VST3. At least REAPER allows you to specify custom paths to vst3 so you can move them around.