Pranshu, what will matter in the end is the leadership that you appear to show. Not being patronizing - just observing.

One of the deficiencies of Scrum is that it downplays the critical importance of leadership, treating the Scrum Master as a glorified facilitator. What is actually need for most (not all) teams is someone who is always aware of what people are working on, and watching for problems.

You point to an example of that: that some people are stuck, but don't realize (until the standup) that someone else could help. The team lead should be observing that they are stuck, and the team lead should be aware of what others are working on, and be able to say, "What about what so-and-so is doing? Is that related?"

Scrum assumes that the team will think of that on their own, but IME they often don't.

An effective team lead is not a bottleneck. Others can and should be thinking of how their work relates to others. But people get very focused on completing their story, and forget what others are doing, or don't pay attention. It is really, really helpful to have someone who is a kind of "expediter", always watching for things that are being overlooked.

Again I congratulate you for trying different approaches, and showing leadership, which is what teams need. Every team is different; and what teams need often changes from one month to the next.