Fact is a micro is not a PC, there is no standardization, only across the same line from the same vendor
That is exactly why I use a third-party IDE/Editor. In my case it's Slickedit but if could be VSC or Eclipse or whatever floats your boat. The fact is you're going to be spending most of your time editing, so something you are used to and can drive blindfold would be ideal for any and all projects. It won't happen if you use ANOther manufacturers IDE, as you note.
So that's why I suggested you say what's important to you, and concentrate of a solution for that. If your choice of editor doesn't do source-level in-circuit debugging it's not the end of the world - you should need that debugger not very often, and in those cases it's surely not that onerous to just switch to the 'official' IDE just for that. But any serious editor will let you run, say, DBG under the bonnet and likely then provide in-editor source-level debugging anyway. If it's a proper developers editor you'll be able to run CLI commands from it, so the edit-compile-fix cycle can still be done in that editor.
The massive advantage of that approach is that you won't be here asking this again because whatever you are working on, your tool is already sorted and will be the same for all of them. It's just the compiler and flasher/programmer commands that change, and all that should involve is a profile in your editor.