A lead dev isn't necessarily a team lead. They could be a technical lead, or an architect, or simply a senior dev with deep knowledge of one specific project. They may not have the interest, skill, or authority to deal with the situation. Even if they can do it you may be pushing them towards quitting or burnout; or creating a feedback loop where their technical contributions drop because they need to coordinate more people because quality is dropping because your top dev's technical contributions dropped.
Sounds weak. I wouldn’t call that person a team lead or a lead dev.
Agile doesn’t take much effort if you know what you’re doing. It’s just a card wall, standups and a planning meeting. This is not hard for a good lead dev. If you think it’s hard, you probably aren’t a good lead dev, or you don’t know how to do it right, which is the same thing.
