from the perspective of managing technical teams i've only found the "manager's schedule" (as described) to be a bother to _me_ and _my_ time management. this has been a major pain in the ass when i had to kick out feature work and caused me to spend several super late nights to wrap things up. this didn't affect my team directly; no doubt my exhaustion impacted my mood and thus my interactions. not sure if i was a total dick (never got that kinda feedback, direct or indirect...but how knows...), but i certainly more than once had the posture of defeat as i shuffled from a pairing session to a strategy meeting.
i tried my hardest to create a big sandbox the devs could own and (mostly) self organize. with the help of sympathetic product managers we switched from scrum to kanban and dropped physical standups (and their associated shitty conference call experience) for a dedicated slack channel. we leaned heavily on tech and a couple basic asks such as "try to post status around the same time every day", "important communication goes in email, not in slack", "if you know your schedule, add it to the team calendar" and so on. it was not perfect but it worked out...for the that team, project and business conditions.
now, i have also certainly (and most commonly) experienced shitty remote situations where people on the speakerphone are forgotten, work from home is viewed as a negative and local time is gravely disrespected.