The Haiku project has not enough people to even keep their servers running. Don't expect them to deploy new services anytime soon.
In general, don't rely on the Haiku project to handle everything. Set up something, and if it works well, they may adopt it.
Does BeSlySAT even perform that "settings backup" service? I thought it was just collecting informations about the hardware?
The idea of automated bug reports has been raised quite a few time, and I'm still not convinced it is the right way to handle this. A good bug report is one with precise steps to reproduce, useful crash logs, etc. This requires interaction between the user reporting the bug, and the devs trying to fix it. I think with an automated solution, people will just click the "report a bug" button and never worry about it again. Did you ever check what Microsoft does when you send a bug report from their similar window?
We are lucky to have several users actively testing and reporting bugs already. We trained them to make good bug reports. And they got so good at it that the developer team has enough work for the next few years already. This raises the question of who would handle a massive amount of bugreports, of which many would likely be duplicates of existing ones. We would need a group of people willing to triage the reports, investigate reproductibility, etc. Otherwise, the data will not be exploitable.
(also, please do use categories when posting messages to the forum - I edited your post so it is in the right place)