no, and I don't want to do that, but probably there may be others that want it (CC @idgserpro).
the pending stuff is neither a problem for me: typically minor Plone releases are bug fixes that should not break anything; that's why we can test on the last stage only.
major release are already covered in our schema: we already test against Plone 5.1 for instance.
This jobs are not actually meant to replace your CI, you don't want to block a pull request because it does not work on an unreleased version of Plone, but the use case, for me at least, would be to use it to check if some new features that got added into Plone recently break your add-on, so you have a heads-up before the final release.