answering the question, no.
why would anyone assume that an increase in licence cost would make anything change.
that would seem to assume that the reason for not fixing bugs, not listening to users concerns, not updating previous versions(ie API 1 in 19r1) or not adding new features, is only due to the cost of the licence.
I do not believe the cost of the licence has ever been a factor in changing the roadmap, or any other issue mentioned above, but if that is true, it is not something ever intimated by the company its self (obviously).
I would like to believe the roadmap is based on a solid strategy which understands the market and user base requirements…
but what appears to be going on (to me, my opinion only) is android and API2, when perhaps many people (who express an opinion on this public forum) want is top quality iOS, web and API1 bug fixes and feature additions.
I have no interest in android(which I know is completely irrelevant), the few apps I make in android are done with a very good BASIC language compiler, none of the apps pay anything after their creation, I have found its impossible to make money from an android app unless its to support a bit of hardware I make, in my limited experience android is not worth more than the 90 I paid for a two year update subscription to the other compiler, I hope the android version in Xojo is as fully complete and easy to use, debug and has the same support and cost that the other compiler is able to afford.
if it is as incomplete as the iOS version we have now it might be less welcomed than other offerings the are well matured.
the iOS version is 299$ and appears to be non optimal, I hope the android version is absolutely feature perfect, has no need for any third party plugins and is provided free licence in the same way raspberry pi is, as no one will pay for that licence either.
As for API2, I am unable to be at this time positive.
for me I would like to pay the same (and not inexpensive) cost of a PRO licence which has a really stable Mac, Linux, Pi, win, web iOS and console platforms all using API1 with the option of using API2(based on OS target) where it is absolutely necessary due to OS requirements, and that being a selectable choice, not forcing depreciations to be churned out or having no choice about changing event names.