Even for Software engineers, I see very few positions which can be fully WFH. If you are newbie, it's better to come to office. If you are a tech-lead of a big team or above, it's better to come to office. Only the independent junior engineer role seems to be a good fit for a fully remote setup.
Onboarding can be done remote, but the best is to schedule extensive meetings / pair programming, or even just a virtual room where the newbie can work independently but ask the senior "as in the office". Or even very clear directions on when to reach out if nothing else is possible.
What happens instead that the newbie is expected to handle all the responsibility of reaching out, and when that inevitably fails the conclusion that's reached is that wfh is not for onboarding.
Seniors typically are already overloaded with keeping the product running and backfilling for the departed colleagues (who are being replaced by the new employees). So using words like "decency" is sure to piss them off even more.
It's not about the people. It's about the position (unless the person identifies that they should not do X because they are easily distractible, but then, that's where the business case comes in). If a position is deemed able to be WFH, then the position is WFH. If a position is not, then it is not. Based on duties and expectations.
Management is about setting expectations and measuring outcomes while providing appropriate support for staff. If the expectation is that you can work from home and produce at a consistently acceptable level, then that's great. And when the easily distractable person falls behind, you either develop them, or get rid of them.
That's not heavy handed management. It's just management. If it's too heavy handed to measure how productive people are in some fashion, then what even is the point of management?
The thing you said just seems like avoiding measuring someone's output and avoiding confrontation. It sounds toxic.