Guys, I'm learning, and yes, this is not commercial, just trying to learn something new. So, please, don't be so hard on me.
It isn't about being hard, it's just that you change things on your system that are internal to the library and not expected to be modified. Sometimes such things are needed, but usually you should do these kind of things if the benefits outweigh the risks by a large margin and you understand the ramifications. The second is definitely not the case and I have my doubts about the first one.
Bad ideas won't get any better by pampering egos. Better learn to do things correctly, even if you don't have to.
Now, before you go out and get more lipstick to paint on your sow, you should take a step back and refocus on the problem you're trying to solve, what are the current problems and the expected improvements and how to measure or verify it. Then you can check if the current way passes those tests or if not, what are better alternative solutions. That would be a more professional way of doing it, where you gather facts on how well your solution works and you don't have to rely on hopes, wishes, religious beliefs or voodoo.
Korman