While I appreciate the sentiment, I don't think PDF is the way, at least in the way you're currently doing it. PDF maybe supported by browsers, but they're not intended for it, it's secondary feature. Same for search engines. Same for mobile.
Most browsers have Print to PDF. If you want people to be able to download an immutable version of your content, then just have a simple static version of your page with a valid print css, better yet, leave everything default.
There are also other lightweight alternatives. The Gopher protocol has a small, but disturbed following : http://gopher.muffinlabs.com/gopher.floodgap.com (you can actually use netcat as your gopher client). Gemini is a more modern gopher-inspired protocol https://gemini.circumlunar.space/. Personally, I'd be pleased to see a text-first approach gain adoption. I don't think anyone looks at the thick-client model browsers have evolved into and sees an optimal solution.
I think evangelistic energy should probably be directed at complaining to organizations that share content through JS-framework monstrosities. Getting rank-and-file web-devs excited about lean websites doesn't hurt, but clients and CTOs have real decision making power.
Most browsers have Print to PDF. If you want people to be able to download an immutable version of your content, then just have a simple static version of your page with a valid print css, better yet, leave everything default.
If you want to fight churn with PDF, just have a simple HTML website with a link to download a versioned PDF of your issue. Your website can be as simple as https://motherfuckingwebsite.com/ or https://bettermotherfuckingwebsite.com.