I generally feel fine if I can preview the payload and it doesn't contain too identifiable stuff. Even better if you can redact fields.
NewPipe has a simple implementation of this where it just opens up your email client with a pre-filled body.
I'm hostile towards telemetry by default because of how much spyware there is in today's technology. I'll only allow it if it's reasonable ( e.g. a GPS getting your location, system diagnostics for software devs ) and it's consentual.
GPS is "passive". It's basically (i'm oversimplifying) sitting there listening to the satellites each broadcasting info, then triangulates itself based on the passive receipt of that data.
I love how you're implying a bug will never get fixed because I, of all people, am not using telemetry. If it's bugging you so much that's when you open up a ticket on their issue tracker.
Nothing automatic, if it's a serious issue I'll replicate on a controlled environment if they need dumps, but usually a bug report with steps to reproduce is sufficient.
I'll happily allow telemetry if its an open source piece of software that gives you the option to "preview" what is being sent (and preferably, not automatically, but as a "Here is what we've got, does this look good?" thing). I'll have a look, make sure its nothing confidential, and send it.
Steam does this with their hardware survey, Fedora does it with its crash reporter system (as did Ubuntu when I used it long ago), and actually macOS was usually pretty good about this too from what I remember (though macOS of course isn't open source).
I prefer to avoid any and all telemetry. I'll tolerate some mandatory telemetry as long as they're honest about it and it's not invasive, otherwise it's just spyware.