No, that's appeal to popularity fallacy.
Let's say some non-trivial segment of users say their unlucky number is 13. Does that mean Bitcoin Core should support a configuration to censor transactions that contain the number 13 in them?
This looks reasonable to me.
https://github.com/bitcoin/bitcoin/pull/33453
Even though I think this drama is largely fueled by social media outrage algorithms, there does appear to be some non-trivial segment of users that wants to keep these configureable options. Just let them have it?
(Via nostr:npub1zsu6h4pfsyt9atxv6prt64j645vlyv22jwkeh5y6mqlrxs47ex0svkk4em.)
Discussion
I’m not saying they “should”. Bitcoin Core developers have no such obligation towards me or anyone else.
I hope they follow their own best judgement even in the face of populist mobs on social media or elsewhere, and set defaults accordingly.
But if they are willing to build and maintain configureable options, I’m generally not against that either. (Not even if these are somewhat or completely irrational, like in your example.)
Since this configurable option only creates downsides from changing its default, why should it exist in the first place?
Basically, if users want to shoot themselves in the foot, and get mad at software developers if they can’t do that… I don’t mind developers giving them an (optional, non-default) footgun.