Should it also include LocalCDN WebExtension
LocalCDN is an interesting plugin for our use case because many sites take for granted that clearnet CDN's are reachable regardless of a proxy server or overlay network. When an I2P node is not configured to use an outproxy, this can lead to reduced performance and functionality for I2P sites, and leaks information to the CDN itself and any outproxy that is configured. Of course CDN's are used to track browsers across the internet. Besides that, an outproxy operator who also observed traffic to and from from a clearnet CDN could potentially discover information about users browsing habits, or use it to discover misconfigured sites automatically(Where a "Misconfigured" site is defined as "Depending on a web browser, clearnet CDN, and a working outproxy"). Besides that, it's a basically unnecessary load on outproxies and their operators. Of course I haven't surveyed them, but I seriously doubt that outproxy operators are super concerned with providing people access to akamai or googletagservices.
LocalCDN could reduce the amount of traffic that goes over outproxies bound to CDN's, and do so on the client side so that it never touches the network, and so that they don't have to count on the outproxy operator to block it themselves, because most clearnet CDN traffic would not leave the local host where LocalCDN emulates it.
https://addons.mozilla.org/en-CA/firefox/addon/localcdn-fork-of-decentraleyes/
It is an Open-Source plugin under the Mozilla Public License version 2.0. AMO says it currently has about 5000 users. The source code is available here: https://codeberg.org/nobody/LocalCDN. It appears to have an active maintainer. It has advanced configuration options, but it doesn't require any configuration by new users to do it's job. We would ship the AMO version, therefore the extension would automatically update itself independent of browser profile releases.