I completely disagree. Employment is a two-way marketplace - I'm looking for an employer, and employers are bidding on what I'm selling: time, knowledge, and experience. They are bidding against not only employers local to me, but with all remote employers as well. They're free to choose someone else to work for them and I'm free to choose someone else to work for.
"Competitive local rates" are appropriate for people whose choices are local. As a developer, my choices are global. Those are very different markets.
I live in Harrison, Arkansas and I make significantly more working remotely than I could make locally. When negotiating salary at my current job, I recall my exact statement to this effect: "I'm not expecting an offer with a base salary equal to what you'd be offering me if I were in Santa Monica - but I'm also not willing to accept an offer that's the same as what I could make working for a local company. I'm confident that we'll be able to meet somewhere between those numbers."
It's also true that many companies try to get away with cost-of-living adjustments, but you can find plenty of companies that don't do that. So they can just keep looking until they find a great offer.
Why would I work 40hrs @ $100 when I can do 10hrs @ $400?
When you're a contractor, you can earn a lot of money for short-term projects, but it gets a bit boring after a while. You're more of a mercenary with no long-term interest in the project. I've also found that the projects are usually very dull. If you join an existing project as a freelancer, then the code quality is often very poor and there can be a lot of technical debt. (YMMV.)
So sometimes it's nice to join a team and have a vested interest in the project, as a co-founder or an early employee. (I've been a freelancer working 10 hours per week for the last few years, but I'm now thinking about a full-time remote job at a startup.)
Consulting is fun, but if you're going to take it seriously (e.g. paying off the mortgage on a house and saving for retirement), then you have to put in a ton of hours over a few decades. That means working on a lot of really boring and tedious projects (and maybe a few interesting ones.) I'd much rather join some startups and get a few "lottery tickets", or build my own projects and support them with part-time consulting work.
I've not had an employer concerned about the number of hours I work in a given period in a long, long time. They're concerned about productivity. Whether it takes me an hour each day or twelve hours each day, if project goals are being met and I'm making them money, they're happy.
But they don't have the same experience and skills. Are you suggesting that all workers with X years in X technology are interchangeable?