Exactly, if it’s such a PITA, you could just remove the 3rd party string by deleting it from the database.
i really really wouldn’t advise it, it’s probably better to wait that the 3rd party dev addresses this by changing his key which also means that need to adjust any usage and also that he‘ll need to remove his duplicate string from them database:) or just to use the existing one from the core , but this also requires the manual cleanup and to remove the existing string... this was improved fror 4.5 , but it’s not backwards compatible and until it’s released it’s unfortunately a step which we but also 3rd party devs have to keep on mind😞
You can see our own cleanup steps in the Upgrade scripts where literally any deprecated or duplicate string is being removed manually 🙂