If you do decide to include telemetry (which I have pretty mixed feelings about), please consider making it opt-in instead of opt-out. Opt-out telemetry is difficult from a privacy perspective because its often implemented in a tick box somewhere in the menus. Many people don't see settings like that down in the options, and ultimately don't know that data is being collected (because most folks don't read license agreements/privacy policies) or that they can opt-out.
I understand that telemetry can be really useful to developers, but when I'm evaluating new software its often a deal-breaker for me. One of the great strengths of JRiver (for me) is how self-contained it is and how little "phoning home" it does. Anonymizing telemetry data correctly is hard, and many developers do a really bad job of it (if they try to anonymize it all), so I just try to avoid it when I can. I'm sure JRiver would do a good job with it (you all are awesome), but it still makes me uneasy.
As a general thing, I try (where possible) to avoid using software that collects data about me, especially when there's no way to validate from the user side what is being collected and that the data has been adequately anonymized, etc. I also take active steps to prevent software from phoning home (via network controls) where developers don't allow the telemetry to be disabled (like with the latest Windows).
So I'd vote against telemetry in general personally, and strongly vote for an opt-in design if there will be telemetry so that only people who affirmatively want to contribute data will contribute.