This sort of situation is bad for everyone: People get their workflow broken, devs need to do work to remove and later reinstate a feature, and privacy-minded people who want to complain need to share name and email to sign up on a forum for an account. In addition, it is hard to gauge what significance the forum posts have: If 100 people are complaining, are they a vocal minority of the millions of users Audacity has, or are they representative of most people?
This is especially true considering Audacity is the sort of casual "useful toolbox USB stick" program for many people - they're not going to closely follow development and updates or participate in polls or surveys, simply because it's not a part of their life they care about that much. This situation is different for something like Blender in which the tool tends to be a major part of your hobby or job if you use it at all. Although, saying that: This is a hypothesis based on my perception which cannot be verified as neither Blender nor Audacity track this data.
With telemetry (which for Audacity would have been a "do you want telemetry yes/no"-type dialog on first launch) the question "does anyone actually use the cut/copy/paste buttons?" would have been answered with "actually, yes", things would have been done differently, nobody's workflows would have been broken, and privacy-minded folks would not have needed to put emails on a forum which may or may not get hacked in the future.
In some sense, even people who disable telemetry benefit from telemetry being an option - assuming that their needs are in aggregate otherwise similar to the average user.
> Audacity's source code is currently released under the GNU General Public License version 2 (GPLv2). We intend to update the license to GPLv3 to enable support for new technologies not compatible with GPLv2 (i.e. - VST3, which is compatible with GPLv3).
VST3 is dual licensed with some Steinberg license and GPLv3. The purpose of the CLA was to be able to migrate Audacity binaries to GPLv3 with VST3 support. This has happened as of Audacity 3.2.
Other uses for the CLA are to publish the thing in app stores down the road. It's not stopping Audacity being open source, unless you consider Apache software not open source.
> The CLA also allows us to use the code in other products that may not be open source, which we intend to do at some point to support the continued development of Audacity.
I am well aware that you're allowed to do this with permissively licensed code, too.