It's also worth pointing out that this whole thing is dramatically evolving. It may be that you're a more "expert" developer and doing the more complex problems that means you're effectively lower in the queue (harder to mentor than basic solutions). Things like https://exercism.io/blog/automated-mentoring-support-project aim to free up our mentors to give them more time to deal with the harder problems. And things like https://github.com/exercism/exercism/issues/4658 and https://exercism.io/blog/track-anatomy-project aim to make mentoring easier and more enjoyable, which means we keep mentors around for longer and they mentor more because it's more fun for them. It may also be that you're on a track that has had 5x or 20x growth (I'm not sure if there are any but you get the idea) in which case the speedbump might have corresponded more to the growth of that track than v2.
If you don't mind telling me your exercism handle, I'd be interested to dig into your situation further to understand why you hit that speedbump. It's easy for me to talk in terms of data, but I'm limited to seeing the general patterns rather than hearing real people's stories such as yours, so it's really valuable for me to understand. Feel free to email me (jeremy@exercism.io) if you don't want to disclose it on here :)