I think because most people give very short descriptions in their standups i.e. "Working on x today, with a bit of y, no blockers". Perhaps due to things mentioned in the article, people don't want to or feel the need to invite feedback
Where I work everyone will do their check-in but the important part is that everyone has a different personality. Like some people can be more confused and have a hard time explaining or even remembering what they did before so it's helpful to ask questions during their check-in to see if they need help. Some people might work on the same task for weeks. People are often afraid to ask for help. Or, maybe their task needs to be broken into something smaller given new information. The daily check-in is also a way for them to connect with someone else in the team who can actually help them. I'll tell them to either hang out at the end of standup or schedule a meeting with each other.
Having someone leading the standup, if done correctly, can help hold people more accountable for what their progress is toward the sprint goal and remove obstacles. This is one of the responsibilities of a scrum master although you don't need to be a scrum master at all to do this.
Right, we do a standup, but if you're not careful the updates can be generic enough like "making progress on X" where you still end up working too long without feedback
