I think it's worth remembering that Dan Gill was thinking out loud on Gearspace, 4 years later I suspect Akai/inMusic overall roadmap could have changed dramatically, so we simply don't know what they are currently working on or what their future ambitions are. If you look at Dan's subsequent posts I think it's clear he was 'spoken to' as he starts referring to 'future press releases' and how he cannot confirm anything.
Here's what
Dan Gill said about 3.0:
disk streaming is going to be a 3.0 thing, because in 2.x there's no concept of a 1 to 1 track model, so it's a pile of confusion. for instance, seq 1 can be drums on track 3, then on seq 2 it could be on track 10, or completely different programs entirely.
3.0 will be a 1 to 1 model (like force is now). track 1, when you add a drum kit or plugin will then be on track 1 in all sequences. this is probably our #1 request, actually.
And this:
yea, skins wont happen
the Force is a sneak preview of MPC 3.0's GUI. the mixer is much improved, for example
And this:
For instance, there's no song mode. instead what will happen is we're going to build a proper arrangement view, which will then be for both MPC and Force. MPC will keep song mode as well, for backwards compatibility.
There might be other stuff as well. I couldn't find anything where he specifically stated that the force and mpc will
completely merge, not sure if that's just people extrapolating, Id be surprised if this happens as they would likely want to keep the two ecosystems suitably unique and tailored to slightly different audiences.
But who knows, I think plans can change quite dramatically in the space of 4 years, and it's one thing pontificating in 2019 on what you plan for a '3.0' release, compared to what you are actually able to achieve.