Instead, it is the perpetration of a clumsy method to completing a task.Not in every case. For experienced/professional/power users of any software, what matters is maximizing the information density in time of both input and output. Sometimes the best way to do that appears arcane.
I want to be able to accomplish much in as little time as possible, so I want a high temporal input information density. So that might mean using a mouse instead of a trackpad for precise aiming and scrolling, or using keyboard shortcuts instead of on-screen icons. It might mean there are different mouse behaviors for ctrl-drag, middle-click-drag, etc.
I also want to be able to receive as much information about the state of the application as possible in as little time as possible. Too little density and I have to keep more state in my head and spend time jumping around. Too much density and the senses are overwhelmed. This might mean, for a CLI tool, that zero output is the best output in case of success. But for long-running processes that might be a progress bar under a list of log entries. For GUIs, the optimum might mean that there is a lot of information and a lot of actions on screen with reduced whitespace, which seems intimidating at first but is necessary to communicate the state of the system to the user.
So convincing any power user to "let go" is like asking someone to give up their legs for a scooter. Sure, it's simpler to go places in mostly straight lines with a scooter, but linear motion is only one of the many things people do with their legs that justify the arcane UI of unstable bipedal locomotion. We walk along streets, run along trails, jump over obstacles, dance, spar, climb, swim, etc.
This is not to say that scooters have no place, or that every tool is at a global optimum. But any "different method" that someone wants to propose will very deservedly receive pushback if it does not fulfill the full purpose of the old method.