Do you always know what the legacy behaviour will do though? Nobody stops you from solving this in a more permanent / explicit way: clone repo with too strict version bounds, change it, install from your branch.
The "--force" / legacy option can't tell a difference between "broken solution that will work for you" and "broken solution which won't".
The "--force" / legacy option can't tell a difference between "broken solution that will work for you" and "broken solution which won't".