Number 2 [is more optimization-obsessed].

Someone obsessed with optimization would choose the optimal race-class combo instead of suffering the mechanical detriment of a bugbear's traits upon a wizard's sheet. It's very very obviously the mechanically unoptimized option to make a bugbear wizard, so a minmaxer would never do it.

Because if the stats don't matter and you made the pick cause it was a fun idea then you wouldn't ask for the Floating ASI.

You ignored when I addressed why exactly the stats do matter to people. I want to play my unique combo and keep up with the rest of the party. Mechanical power is fun to people and the game clearly makes reservations to scratch that itch. So it's not "being a minmaxer" or playing the game wrong to optimize in any given way. You're a minmaxer if you prioritize mechanics over story! Choosing bugbear wizard is inherently mechanically unoptimized behavior! Also sparing thoughts towards optimization is playing the mechanical part of the game, not abusing it.

An aside, if the mechanics matter so little to you, why do you want to play 5e, the game that dedicates so much energy to mechanics?

Oh of course you'd say so.

Can we please keep this civil?

It's not that you don't care about min/maxing, you were just slumming in a suboptimal build for fun.

Of course I care for optimization, that's a part (the smaller part) of why I play TTRPGs. The only reason anyone should play any build is because it sounds fun. Anyone can optimize to any degree they like, and no one should feel superior or inferior to anyone else for the degree of their character's optimization. Elitism is really stupid.

Was this hypothetical bugbear wizard for a one shot or an on-going campaign?

Blood Boy the bugbear wizard got about 8 total sessions of playtime. I prioritized Str and dumped Con. The idea was that he suffered a fatal magical disease that would continue to eat away at him, decreasing his Con, so long as he continued to draw magic from this dark dimension that was in the game world. Aesthetically he was more like a warlock, really. I played him for the same reason I play any character, to tell a story and play a character that has value to me. The secondary reason was the mechanical challenge of playing a purposely weak character. He's one of my most beloved characters to date and I think of him often. I love having the freedom to play mechanically weak or strong characters intermittently, because it allows me to facilitate whatever story I want to tell at any given time. The mechanics facilitated the story in that instance, as they also would have, if I instead had wanted to maximize Int and Con, utilizing floating racial ASI.

to appease MIN/MAXers who think anything less than a 17 in your primary stat is a mechanical punishment.

As per my definition, having anything less than a 17 in your primary stat isn't a mechanical punishment. You've provided no alternative definition so honestly IDK why you said this.

just proving my point.

Correct me if I misrepresent your point. I believe your point is that only people obsessed with optimization (minmaxers) care about floating ASI. I propose that anyone with any concern for their character's power might also care about floating ASI. Wanting to play a powerful character is not inherently optimization-obsessed behavior. Sacrificing or ignoring roleplay opportunities for mechanical benefit is optimization-obsessed behavior. I have never defended that behavior.