I don’t think so.
First, to repeat, plugins are blackboxes which follow the protocol. A plugin reports its internal state to the host to save and restore it. Not doing so is calling for trouble.
Maximum you could get is to purge the instance entirely and by option only save changes to those parameters available via Quick Controls. User would have to set this individually for each plugin, which is quite a stretch imho.
Secondly, just run “File/Preload” and check how much memory plugin states of all plugins consume, as saved by the plugin itself - that includes those parameters you suggest to save only. Is it any significant?
Third, the plugin instance itself will be loaded into memory, and that is more concerning with some plugins. For the majority, it is not significant either. Only saving parameters would not help without a purge of the plugin anyway.
And fourth, no inactive plugin consumes any CPU whatsoever, unless activated either globally (then you need it anyway), or by Part, or Song.
I don’t understand what you mean by “load the plugin”.
A plugin consists of two parts, for one, the code (“dll”) which needs to be loaded for the plugin to do anything, and secondly, its state (parameters, internal storage etc). VST Live keeps a plugin loaded all the time, it does not need to be re-loaded. That is what a purge function would do, to entirely remove the plugin, and entirely re-load it when referenced again.
You probably mean the plugin state. Again, check to see how much that really is.
In VST Live, a plugin state is not saved or loaded either (except with file operations), as plugins simply keep their state at any time. Shrinking the memory for a plugin state by only saving parameter changes (which are accessible by the host via “Quick Controls”) will not make much of a difference. If the memory display of the “Preload” functions indicates something different, please let us know.
