Sincerely this cannot be a major item if you design your code in a structured way.
It seems probable that you use a different sw design paradigm from that for which REMIX has been designed.
In that paradigm, the ABI should change very rarely because it specifies the external interface surface of the code. If not, it could means that you change your system structure as methods description (as seen by the system) in order to solve detailed implementation problems and this is, generally speaking and without prejudice, the sign of a possible somehow improvable flow of the design.
In a project interfaced with web and/or physical devices, the very first stable design is that of the interfaces, i.e. the ABI in this case, mostly for an enhanced parallel design (I.e. other designer can go on with their part of the project without waiting the end of your part), but even for test tools stability (thinks to continuous integration). The ABI change should be a major and shared step, to make if some other measure is not convenient for the project.
In order to help, Remix give you all the user interface you can need in order to fix the ABI as first. You can do all you want without external stubs from the first compilation by means of the internal UI for functions test and management.
When it is Fixed the ABI (I.e. methods and calling parameters), you can begin to work deeply.