We have six people in the stand-up.
If you're so sad about being interrupted then maybe you're taking on too much work?
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.
Literally, it's not 10 minutes. Count the time that you have stopped working and people are chatting waiting for the meeting, checking their email when they would not otherwise do so, not working on their main tasks.
20 minutes to half an hour of time not usable for main tasks is a more typical estimate.