That is actually a good idea, but it's the first time I heard about it. In most companies, this is not done. Also, it's not just the literal time of the meeting.

It's the time people spend waiting for the meeting, chatting, reading email instead of working on their main task for the day.

It's about the interruption cost and the disruption of what you were doing, not about the literal cost in minutes.

Also, most developers don't have a saying in how much work is assigned to them. Usually, they are over assigned already and the cost of the standup is not accounted for in how long tasks should take.

Add all standups of a week, and you have half a morning of work per week down the drain. That's a lot and again that is literal total time only, and does not account for interruption cost.