I now strongly believe you're going into a goose chase...
Write this down, will you?
plugin binaries are not portable between machines or (file-)system images, period.
LV2 plugin URIs must at all times be unique and identify one binary instance and only; the host LV2 inventory makes sure this is the case on all times; working around that (like adding several search paths where one and many might be found, at any given time, will lead to the proverbial undefined behavior, that being only one instance will ever get called and it is uncertain which will be, probably the wrong one (in this regard, it all deeply depends on the libLILV implementation in charge).
so, I would recommend to follow not on this idea--is out of (our/qtractor) control--and put simply, it is not just an uphill battle, rather a predictable lost one.
Hold your horses!
I now strongly believe you're going into a goose chase...
Write this down, will you?
plugin binaries are not portable between machines or (file-)system images, period.
LV2 plugin URIs must at all times be unique and identify one binary instance and only; the host LV2 inventory makes sure this is the case on all times; working around that (like adding several search paths where one and many might be found, at any given time, will lead to the proverbial undefined behavior, that being only one instance will ever get called and it is uncertain which will be, probably the wrong one (in this regard, it all deeply depends on the libLILV implementation in charge).
so, I would recommend to follow not on this idea--is out of (our/qtractor) control--and put simply, it is not just an uphill battle, rather a predictable lost one.
hth.
cheers