Let's put it this way: if the button was for something you didn't agree with - say, it was a button for "show your support for the sanctity of marriage", would you blithely say "there are lots of buttons in the preferences so it's weird to get mad about it"? I suspect not. I suspect that you would, in fact, be outraged even though that'd be an equally hidden expression of political opinions. We can't, with any fairness, take a stance that political expression is ok but only if it is for the ideas we agree with. So we should (and we used to) agree that things shouldn't have politics forcibly shoved in people's faces, and that we must live and let live. That's a far better way to coexist.
if I was pretending that my dislike of a button for people to show their support for abolishing gay marriage was rooted in sincere concern for how much time was spent in porting the skin and menu button to another platform versus other more complex features, it would be absolutely right to observe I was being disingenuous in feigning neutral interest in feature prioritization decisions every time I called for it to be removed...
If you don't want the pride skin "shoved in your face", it's relatively easy not to visit the relevant area of the preferences menu and select it, just like people that aren't particularly interested in marriage or Christmas are welcome to refrain from using any of Office's wedding-related or Christmas-related templates
That is what GP is pointing out as far as I can see.
Having checkboxes for fully cosmetic nothings while simultaneously releasing features that cannot be disabled feels strange given they are clearly able to put the required effort in for a hollow, mealy mouthed, capitalistic pandering effort.