While in a robust “commercial” ERP system this might be possible, a volunteer based project like ERPNext cannot be expected to include such strict “ease-of-use” functions.
For the most part, the volunteer developer allocates their time to a fix for a problem and then has to go back to their real life where they can make some money doing other tasks. It would probably be better to set you expectations a little lower to something closer to just not crashing.
I realize this is not “ideal” but this is a bit closer to the reality of how this project works. In the past when I made similar observations I was informed that I could develop the feature enhancements myself and then contribute them to the system. After a few times of this, I realized it was best to be happy that it just worked.