I appreciate your advice, really, but by now you must know I already know what you're talking about, and that your advice covers a design decision that was already made several steps back in the development process from where I am today. It's much like telling me I really should go to see Star Wars when I just need to know how to get to the theater for The Avengers tickets I have in my hand. Maybe you're right, and Star Wars is better. And maybe I even agree with you, but my wife bought the tickets online last week and arguing now would be pointless and possibly even bad for my marriage.

Thinking outside the box and looking for XY problems is great. I encourage it, I welcome it. We all need a sanity check now and then. You made your point pretty well eight or nine replies ago, and I'm fresh out of ways to try to either stupidly defend the efficacy of the existing software that I didn't design, or let you know "I agree in general, but my example is specific, and you're ten years and two developers too late for this kind of advice". So I'm not sure about you, but I'm about ready to call it a day and make myself a sandwich. Want one?

Edit: And, sorry I just about missed this twice, but yes, your point about coercions is well made.