I suspect that the concerns above revolve around making sure that reviewers understand the project before getting handed a unit to, 'review'. When receiving an Android or Windows or iOS device, there is an expectation that the device and software are fully realized where the expected changes through time are updates and bugfixes.
The Pyra is different. The initial release units may be hardware that is just out of beta but we should expect software that is alpha grade - at least at first. For example if the reviewer heard, 'it has telephony capabilities' and reviews it as a 'phone' with the expectation of loading their contacts over to it and sending/receiving calls, taking pictures and expecting Google Maps level of navigation, they're going to review it very harshly. If they're into 'fashion & style', forget it. Anyone who could 'score points' by thrashing the device in the cruelest possible manner - not who we're looking for.
On the other hand, if you get someone who understands that the Pyra - at least initially - is a hardware platform for the development of the software to make it 'work'. Basic hardware functionality and Linux OS out of the box, other software to come later. If reviewed as a hacker/developer/retrogamer/emulation platform, that might be better. But - it needs to be emphasized that it is the realization of hardware that will enable the beginning of the community-side software development stage.
Yes, quite a bit of software development has gong on behind the scenes - likely much more than I am aware of - and thank you one and all who have done so. But - I think that the time for -hardware- reviews may be soon, but the expectation of most reviewers is 'complete device' including software - and I don't know that the device is, 'there yet'.