I’d guess a fairly small subset. Because Audacity is such a versatile application, there are many, widely differing subsets (or as we tend to call them: “use cases”).
One of my favourite features in Audacity is that it has a built-in scripting language called “Nyquist”. Although only a small subset of users are likely to use Nyquist directly, indirectly it is one of the most widely used features. Nyquist is an interpreted language that runs straight from the plain text code (no need to compile), and with the addition of some special “header” comments, can be used by Audacity as “plug-ins”.
Audacity ships with quite a few Nyquist plug-ins. In the Effect menu, the effects listed at the bottom (Adjustable Fade, Clip Fix, Crossfade Clips, …) are Nyquist plug-ins. There are also a large number of optional plug-ins available, many of which were written to provide functionality required by subsets of Audacity users: Missing features - Audacity Support
Plug-ins are a very good way of providing functionality that is required only by a subset of users, as it avoids adding “clutter” for other users. It would be nice if installing Nyquist plug-ins was easier, but we’re working on that.
Perhaps won’t need to if we can provide a plug-in to do the job.
Originally the Audacity wiki was like Wikipedia in that anyone could set up an account and post directly to the wiki. To combat spam, restrictions on accounts were progressively increased, but even when manually verifying that user accounts were genuine, a lot of what was being posted was written so badly that it was often incomprehensible. We do not have the resources to adequately monitor, edit, rewrite submissions to a public wiki, so it is now available as a read-only addition to the manual. There is still a huge amount of cruft in the wiki that needs updating / revising / deleting, but the priority for the documentation crew is to keep the manual up to date.
Our preferred way for Audacity users to submit feature request is via this forum. This allows Audacity users to comment and discuss feature requests before they are transferred to the wiki. A large number of requested features are for things that Audacity already has, so feature requests sometimes mutate into a discussion about how to improve an existing feature.
Thanks for the link. That’s a pretty old page, and it has a note at the top for wiki editors, indicating that it needs some TLC. I’ve put that on my to-do list.
You’re very welcome. Thank you for your feedback, and my apologies if my initial reply appeared dismissive - that wasn’t the intention, but even emojis are limited in their ability to express mood 
I’d be interested in your feedback on the Nyquist code that I posted - if it works for you, then I’d be happy to turn it into an installable plug-in and post it to the wiki plug-ins page so that it is available for everyone.