What Do You Want To See In A Roadtest Review?

I think the best reviews are when someone manages to combine multiple categories - do a cool project which also is a good tutorial (so not only show the project, but also explain how its done), or use a project to demo a functionality of the RT item (and in the best case its a tutorial on how to use this functionality ;-). Buts difficult to do, and not always possible.

Good list. I will keep that in mind for the next review.

Generally I would like to see more demos of usage in real applications and descriptions of the experience - what went well, what was tough and why, what they liked and didn't like and why. Maybe comments on how it  could be improved if there is a serious deficiency.

Generally I don't need someone to try to prove that datasheet specifications from name brand instrumentation are accurate - using hobbyist equipment.

I definitely don't need the road test to dwell heavily on the brochure features list although mentioning the differentiating features is a good thing to do.

A discussion of the range of applications is always good, especially those applications where it excels.

It depends on the product being reviewed. But sometimes I do feel lost that I have done too different roadtest of products. hence things like "Summer of FPGA/Sensor" will help as there is more specific content and direction to improve ourself.
Recently, I saw some programs on hackster where they provide some microgrants  to finish-up the project with the product the roadteste sponsor offer. This helps to buy components needed to create a good project.

I was deciding between More benchmarking and more tutorials. Finally, I voted More benchmarking because benchmarks are always cool, but it is hard to do benchmarks. I was considering tutorials because Roadtests usually targets new items on the market and frequently there are very few existing tutorials.

This is a difficult question, the answer depends a lot on the product being reviewed.