> That doesn't clarify as "customizing my environment" is more like "fixing fundamentally broken shit".

I mean, sure, if you define any config change that tangibly results in higher productivity and better performance as a fundamental bugfix instead of a customization, then customizations don't matter.

But that seems to be a kind of arbitrary distinction. Just as an analogy:

----

"I lost 30 pounds and fixed a sleep apnea problem when I started paying attention to my diet."

"That isn't paying attention to your diet, it's fixing a fundamental health problem. In general, most dieting falls into the category of fads and micromanaging."

----

Aside from your specific definitions about what does and doesn't count as customization, what do you and the OP actually disagree on?

Do both of you agree that when changing an Emacs config, I should take into account the ratio of time they'll save and the time I'll lose making them?

Do both of you agree that there are changes I can make to an Emacs config that would eventually provide a net benefit in terms of time saved?

Is it good that I can make those changes that save me time in the long run?

Is it bad if I ignore the cost/benefit analysis of a customization and spend more time messing with configs than actually programming?

I don't understand what you're actually arguing about.