I accept you're a gifted coder, and that you're better than your peers. Good, then do exactly that.
Being good at mentoring people is only vaguely correlated with being good at code. IMHO, the main factor that will make you good at something is caring about it, and if you don't want to talk to people you'll waste your skills.
There is someone out there who would love to talk to people, worry about their development, figure out how to best use your skills and so forth. Let them do it.
sounds like a good time to work on a harder problem :) OP is crushing it on their product. Given the OPs description, we can also infer that the OP works somewhere that commits correlate with output well.
A few interesting questions that come to mind.
1 - Does OP feel like they are doing the same things over and over again?
2 - Does OP want to work with better/more skilled engineers?
3 - Is OP setting the technical direction? Do they want to?
Being the top coder by commits in a group of 350 is a super power, however many "Hard" software problems are resistant to code throughput as a fix. There are extremely difficult software problems that take years to produce the ~1k line solution.
I accept you're a gifted coder, and that you're better than your peers. Good, then do exactly that.
Being good at mentoring people is only vaguely correlated with being good at code. IMHO, the main factor that will make you good at something is caring about it, and if you don't want to talk to people you'll waste your skills.
There is someone out there who would love to talk to people, worry about their development, figure out how to best use your skills and so forth. Let them do it.