Hello to whoever is in charge of MDN policy,
As such a user I have in the last year or two noticed that some of the bugs I file against MDN are met with a reply along the lines of ‘your use case is not important to us, because most of our users are web developers and so don’t benefit from <whatever change I suggested>’. (E.g.: re: links to older versions of the spec, re: polyfills)
In each case the reply is pretty reasonable in its individual context, but I think there is a danger that the “this feature is not useful to our core audience” attitude becomes self-fulfilling, because my experience has been that MDN is becoming less useful to me (and therefore, I posit, to other non-webdev users).
The ultimate result is one less non-webdev user, and so even less reason to maintain whatever useful-but-not-to-webdev information remains. Not coincidentally, it also means less pair of spec-savvy eyes to spot, report and/or correct incorrect or misleading information here.
What audience MDN chooses to cater for is of course up to you—but let me suggest that the audience you have served in practice has historically been rather broader than the one you now appear to be focused on, and that being a little less narrowly focused could increase the total value that MDN provides for comparatively little additional effort.
Or, tl;dr: please don’t keep deleting information from MDN just because it isn’t useful to web developers.