Perhaps, but then, build backend is by far the easiest one here. Almost by definition you are a more advanced developer at this point, and should be quite satisfied with a decision tree that filters out “need native extensions”, “needs to generate/relocate files on build” and then tells everyone else to choose one of the remaining 4-5 options based on style.
It basically boils down to Project Summaries - Python Packaging User Guide but arranged by category and linked more prominently. I don’t have any problems with letting the backends self-promote in this kind of context - they’re the most motivated to commend themselves to potential users.
But I don’t think it’s a good idea for this ad-hoc group of contributors to vote on “who wins”, which is what any “official” recommendation from PyPA would boil down to. Listing the known backends that all fundamentally work the same is better - or possibly a feature matrix to make comparisons easier.