This is again another good example. Process is there, devs dedication is there, users dedication who participate in testing is also there. Is Asobo wrong? Clearly not. But if results are not efficient because at the end devs have to deal with a ton of requests that need further filtering then the process is not followed correctly, even if it was defined. When it was supposed to be helping to improve it turns to create more complexity than it should and extra work for Asobo.
One solution is what you propose but other is that Asobo defines how testing shall be done, instead of leaving it open to free interpretation from users, who in many cases may not be even familiar with software testing itself. So to define the test cases that shall be tested instead of saying “guys, free fly and report what you see”. We have a template for bug reporting, so one of the problems (what to report and how to report it) is already addressed.
With proper testing instructions info reaches devs in an optimal way and everyone is following a defined test cases list. Then you can compare if results are different depending on Xbox or PC, depening on the GPU or the MoBo settings/drivers, etc. Leaving it unguided (open to public without clear instructions) and like wild west helps to detect that an error is there but not why it´s happening or what exact combination of events triggers it. It still helps, for sure. It´s good for overall testing, sure. It´s also cheaper, sure. However is not 100% efficient.
Cheers