Sounds a lot like me a year ago.
For the past eight years I've been mostly working as a .NET developer, with my last two roles being senior roles with some form of leadership. If I stuck with my last job I would've probably been in a leadership role at a large agency, but I wanted a change.
I, too, would read HN most days, and would feel a hint of "imposter syndrome". It was great enough that I decided to teach myself Python and Django. Working in another language when my life was strong-typed compiled languages felt odd, so instead of fighting the urge I decided to work somewhere that would hire me as something other than a C# dev.
So, I joined a software house that does a bit of everything. Since joining I've worked on a mixture of Ruby, Java, Python, and Node projects in the last six months, and there's opportunities to pick up pretty much anything that I feel I can roll with for a project.
It's been tricky going from being experienced in one language to being a newbie in another. When things work the way you expect, new languages are fairly easy to pick up, but the pain points or differences will bring you back to the days when you were struggling with C#.
I think imposter syndrome is more common in .NET developers than other groups, mainly because the community is so secluded from others due to its heavy use of Windows and its own tool set. Also, there's the stigma of it being a big-business language, even though many .NET devs will go their entire careers without working in an enterprise setting. From my experience, a .NET developer is no less a developer than those in other languages, but I will say that it's very easy to be comfortable in a single stack. Giving something else a try will reduce that comfort, and you might learn a few things that help in both stacks.
So, in terms of missing it, it depends on what you feel like you're missing?