Except it is Maemo, it has far more in common w/Maemo5 than vanilla MeeGo.
Of course it's not (as) compatible w/Maemo5, the goal was to maintain compatibility between Vanilla & Harmattan.
Have you ever used MeeGoCE, now known as MeR/Nemo???

Nope, it makes little sense to refer to at as MeeGo because the MeeGo project is dead.
It was part of the project & was designed to enable a gradual transition to MeeGo proper.
But as that project now longer exists it can no longer perform its role, so it makes little sense to refer to it as MeeGo.
In a technical sense there's no question that it has much more in common w/Maemo5 than Vanilla MeeGo.
Even Nokia tellingly re-geared its marketing plans last year by tacking Harmattan onto the end of MeeGo.
But I don't care either way, people can call it MeeGo/M-H/Harmattan/Maemo6x, doesn't bother me
I prefer to call it Maemo6x because it makes more sense to me, but the general public couldn't care less.

I mean the road-map that was in place just prior to Elop-fail announcing the new plans on Feb 11 (?) 2011.
The 1st x86 (Read: Intel/medfield) ph was due in roughly Dec 2011, it's clear now that probably wouldn't have been possible.
But given what Intel's delivered this year, it's quite apparent that June/July would've been possible.
The plan was always to have at least two Maemo6x phones, possibly a third if MeeGo proper & the 1st x86 phone needed it.
So it seems we would've had a 3rd Maemo6x phone by now or shipping, & the 1st x86 would've been announced "roughly" June/July.
This is all assuming of course that the team remained at full size, or even grew slightly since Feb last year.
Instead of dropping by over 75%....

Not really, the main openness advantage maemo5 had was w/large chunks of the UX layer/apps etc.*
Security/permissions framework in Maemo6x is quickly/increasingly becoming less of a hindrance.
Just a few months ago people were bleating that it's "game over" thanks to AEGIS etc.
Maemo5/6 weren't particularly amazing from an openness perspective, even compared to Android.
MeeGo proper would've been far more compliant in that regard...
Now that Intel & co's transformed it into Tizen, lets hope they actually make it a success this time.
It has it's drawbacks that vary in magnitude depending who you ask, but I'll be giving it the benefit of the doubt.

*I'm not understating that, it is a "biggy", but still somewhat of an open question.