Installing plugins without regard to max version

(M Herger suggested I post this proposal in a separate thread. Here goes ...)
There is a parameter setting in the plugins stating the "max version" such as "7.*" which LMS honors and refuse to install or even display in the "3rd party plugins" list. However, they are retained when upgrading LMS if they are already installed. It is also possible to install them manually after editing the parameter, if they can be found and downloaded. So far this has mostly been a matter of alerting the plugin maintainer who after some initial testing (usually) updates the parameter to "8.*" or similar. But some plugins are unmaintained or the maintainer lacks the time and resources to do testing (and consequent maintenance).

With regard to the issue of older plugins not maintained and the "max version" parameter in these, can we not simply delegate the decision to install these old plugins by means of a new preference setting that controls whether the "max version" parameter is honored or not? It is already possible to force an installation manually (after editing some file in the module). If the default preference is "honor the module setting" it would require a conscious (I hope) decision by the user to override it.

Furthermore, bpa's suggestion is excellent:
Likewise mherger's caution:
I am sure there are many concerns with this proposal, not the least that it would risk exposing maintainers to support requests they have no time for.
Still, it would be interesting to hear what your thoughts are on this.