I "think" that's the purpose of this proposal of Blaze 2.0. Otherwise, it would just be Vue support for Meteor.
Regarding Blaze 1 - I believe it's important because while, as you said, Blaze isn't going anywhere, it's kind of at an impasse. It just got switched over to community-supported, but if we think realistically, it's doubtful that anyone is going to put as much work in to Blaze as the developers of Vue, React, Angular, etc are getting.
As much as I would love it if MDG does give Vue the React treatment, I can't say I agree with your first sentence there in all circumstances.
Sure, as a new project, you can use Vue. But there's many situations I could think of that this would not be ideal.
For example, many of us have existing Blaze projects that have been kind of in limbo. I would love to have support for some newer view framework features, but a complete refactor to Vue directly would be a lot of work. But it would be quite an awesome upgrade for Blaze if Blaze still worked and I could simply start using those new features in addition. This would keep projects functioning correctly during transitions to Vue as well, allowing users to refactor their projects over time/as needed, rather than all at once.
Also keep in mind, most new users of Meteor end up choosing Blaze initially. Rather than this being a long-term limiting factor, Blaze 2.0 w/ Vue could allow new users to start almost the same exact way they did in Meteor 1.0, and then as they become more experienced, dip in to the new features.
Not to mention, it's a huge benefit if users have been using Blaze for years, and have collections of different systems/components/etc, and be able to still use them after switching to Vue. Of course, refactors would make them work even better - but just being able to use your old code is a huge boon.
That's true to a point. But with all the potential refactors we have coming up in Meteor, the last thing we need is even more on our plate. If I was going to complain about 1 thing in the state of Meteor right now, it's the worry about major refactors.
Fully viable Vue support, with an additional package that could optionally be added for legacy Blaze support in Vue, in my opinion would fully achieve that goal of the best approach, while helping out all the users who stayed faithful to Blaze (which, according to polls here, is a very large part of the community, despite some comments indicating otherwise).