Switching between tools has a cost, so the tool needs to be not just better than another, but better after accounting for switch cost.
And the cost has to fit in to your budget. I'd rather spend my budget on learning emacs, for example, instead of spending it switching to a new shell.
It depends on your role. Many people regularly maintain or interact with prod deployments which cannot be customized to your liking. So it may be "somewhere" or occasional in your case but not in all cases. Switching back and forth between shell syntax every few hours is very disorienting and worse, can cause serious errors (for ex: if I have a local alias with rm="rm -i" but a prod server doesn't have it)
That's pretty much my argument for choosing Bash over Python for my everyday scripts. It's sensible.