This is not the issue, at least when I talk about myself (I can’t speak for other devs). I fully understand that how things are now is confusing, and that there are both simple-but-already-nice and more-complex-but-even-nicer solutions out there.
What we do need is:
- A proposal on what to fix, and how to fix it. This should includes some alternatives to choose from, or a list of alternatives considered & discarded (and for what reason). Basically what’s described in Ingredients of a Patch; these are nice to have even when there is no single line of code yet.
- Discussion of the proposal. The forthnightly module meetings are the perfect place for this, and I certainly invite people to come and join. If you want to discuss something at the meeting, either pop over to
#animation-moduleon Blender Chat, or wait until the meeting agenda is published in the Animation & Rigging section here on DevTalk and add a comment in which you propose to discuss this topic. That way the people attending the meeting will be aware of the topic before the meeting starts, streamlining the process. - And last but not least, a developer who can implement the changes and stick around to maintain the code after it’s been accepted in Blender.
@NunoConceicao I think you have some nice ideas. Do you have some Python programming skills? If not, may I (tongue-in-cheek) recommend Scripting for Artists? 
Joking aside, maybe my Transform Helper add-on could be used as a basis for the proposal. It’s always easier to talk about features when they can be demo’d, as then everybody is looking at the same thing.