Organizations are generally well acquainted with that sort of "work tax", and the results are fairly well characterized and understood and can be worked around. (Move closer to employees, open a branch office, promote off-peak working hours, transit subsidies).
Remote work is a very recent phenomenon and as such, runs into a completely different set of problems that haven't been as thoroughly solved as a co-located working environment.
It's like picking PostGres/Mysql over Cassandra/Mongo. Sure, both have problems, but the traditional SQL solutions are stable and the problems have known workarounds. With NoSQL solutions, you might be one of the first people who are doing that particular use case, and you'll have to pioneer your own solution, at the expense of the company's business plan/profit.
Remote work is a very recent phenomenon and as such, runs into a completely different set of problems that haven't been as thoroughly solved as a co-located working environment.
It's like picking PostGres/Mysql over Cassandra/Mongo. Sure, both have problems, but the traditional SQL solutions are stable and the problems have known workarounds. With NoSQL solutions, you might be one of the first people who are doing that particular use case, and you'll have to pioneer your own solution, at the expense of the company's business plan/profit.