It works, however, I ask that you reconsider my initial request.
It has some collateral advantages.
It doesn't have the problem of not being able to have different versions of the same plugin.
It facilitates portability. Except for two exceptions: LV2 and plugins that have dependencies (samples, text files, images).
Let's imagine some scenarios:
A. I want to use another computer occasionally. I only need to take the USB drive with a Qtractor AppImage and my projects and plugins in the same hierarchy as on my personal computer. Everything will open without having to configure anything on the destination computer.
B. I'm going to a friend's house, who is also a musician. Here, the advantage of not having to modify their destination configuration is more significant.
C. A music academy prepares the course materials on USB drives for students, with pre-configured plugins and exercises (in this case, LV2 and plugins with dependencies are not a problem, since the content is specific and would be avoided when including them in the exercises). Furthermore, this way students don't have to scan and install plugins, which, although useful for their training, might not be suitable for their personal work.
Etc.
EXCEPTIONS:
The problem with LV2 is solved by reconfiguring the scan path in the destination... It's an inconvenience, but at least it's not six inconveniences (LV2, LADSPA, CLAP, DSSI, VST2, VST3).
Regarding the problem with plugins with dependencies, the only solution is to avoid them as much as possible.
CONCLUSION:
Advantages: The initial request provides a new improvement in functionality, not complete due to the exceptions mentioned, but an improvement nonetheless: Portability.
Drawbacks:
Sometimes we'll find unpleasant and lengthy strings of slashes and periods within the session files.
It works, however, I ask that you reconsider my initial request.
It has some collateral advantages.
It doesn't have the problem of not being able to have different versions of the same plugin.
It facilitates portability. Except for two exceptions: LV2 and plugins that have dependencies (samples, text files, images).
Let's imagine some scenarios:
A. I want to use another computer occasionally. I only need to take the USB drive with a Qtractor AppImage and my projects and plugins in the same hierarchy as on my personal computer. Everything will open without having to configure anything on the destination computer.
B. I'm going to a friend's house, who is also a musician. Here, the advantage of not having to modify their destination configuration is more significant.
C. A music academy prepares the course materials on USB drives for students, with pre-configured plugins and exercises (in this case, LV2 and plugins with dependencies are not a problem, since the content is specific and would be avoided when including them in the exercises). Furthermore, this way students don't have to scan and install plugins, which, although useful for their training, might not be suitable for their personal work.
Etc.
EXCEPTIONS:
The problem with LV2 is solved by reconfiguring the scan path in the destination... It's an inconvenience, but at least it's not six inconveniences (LV2, LADSPA, CLAP, DSSI, VST2, VST3).
Regarding the problem with plugins with dependencies, the only solution is to avoid them as much as possible.
CONCLUSION:
Advantages: The initial request provides a new improvement in functionality, not complete due to the exceptions mentioned, but an improvement nonetheless: Portability.
Drawbacks:
Sometimes we'll find unpleasant and lengthy strings of slashes and periods within the session files.
I'm simply asking you to weigh the pros and cons.
Whatever you decide, I'll be happy.