That said, if you want Mozilla (or other organisations, for that matter) to make decisions based on how you're using their products, then it doesn't seem like an unreasonable expectation from their side that you tell them about that usage, i.e. through telemetry.
At the same time, people disable telemetry because as we've come to understand much more clearly as a society (and some of us already knew long before "recently"), there is too much data floating around about us as it is. Not all of it stored in a secured, anonymized fashion even if the organization in question claims to. People are skeptical of automatic telemetry data collection for good reason.
It's more them asking specific questions for preexisting objectives - and my browser answering them, often without me even knowing the questions.
From where I'm standing, your comment is straight out of Kafka. You just apologetically ("I'm afraid") keep insisting that the hostility being experienced is "the best way to deal with this."
What is your source for the proposition that Firefox gains from removing RSS?
What is your source for the proposition that telemetry is superior to randomized user surveys?
Debian's popcon survey has a worse version of this problem: it reports back the packages in use -- and nobody setting up a bunch of servers wants to leak that information, so they only get home users reporting in.
I think removing little used features is a good idea, else you slowly build up more and more things, and one thing I've learnt is that these little used features can end up upsetting more users who accidentally activate them, and are confused, than they have happy users.
The GP noted that the more concerning thing going away isn't Firefox presentation of feeds (the live bookmarks) bit the discovery. So far, you can use the orange button to learn which page supports RSS or even learn that RSS exist in general. Without that button, even if there are extensions, only people who already know what RSS is will be motivated to install them.
Now we get that kind of default discoverability instead for proprietary services like Pocket...
A low-maintenance compromise would be to keep the button, but make it strictly extension-only. Provide an API/manifest entry where an extension can register as RSS reader. If the button is clicked, that extension gets a callback. If no extension is installed, open the Browse Extensions tab and offer an option to hide the button.
The Firefox devs would still need to maintain the button and feed discovery logic (which mostly checks for a specific meta tag, I think) but could still throw out live bookmarks, the Atom parser, etc.