Yes. There are still projects out there that are on M3. (E.g. spring-security).
Perhaps these people can be expected to move on "soon". But the truth is that if there builds are working fine, they may be reluctant to tackle the upgrade.
This problem is quite serious to me now that the method has been removed in M9, I either have these two options:
1) people with M3 projects can no longer run/view any tasks (which also breaks import if those project's import relies on executing some tasks).
2) continue to stick with tooling API M7
So to me that is a real blocker for moving to Tooling API M9.
For now I'm going with (2). But if EclipseProject.getEclipseTasks is put back in some snapshot build. I may consider basing the next STS-Gradle support of off that Gradle snapshot build instead.