> patching bytecode
There is a lot less patching bytecode going on now, and it is now handled by Forge.
> unofficial APIs ... like Minecraft Forge
Unofficial APIs are what happen when nobody else provides them. It's far too late for any "official" mod API that isn't Forge, because the massive[1] amount of modding that already exists is just not going to be re-written.
The best thing that could happen would be to bless Forge as "official".
I also agree that, by default judgement, Forge basically is the modding API at this point. But I disagree that blessing Forge as official is the way forward, precisely because of how tightly bound it is with the existing structure. How well would Forge be able to integrate with this new C++ version? Who knows! So, yes, use Forge as a primary input or even a starting point for a true official API. But don't just blindly bless Forge.
... That's exactly what the word "completed" would mean in every other context. Things are typically not called "completed" unless there is no more pending work on them. I would maybe look at terms like "feature complete" as an alternative here, where the intent is that the only development will be in maintaining compatibility with future releases.