This exactly, sometimes you have to use something not because it is the best option, but because it is what your team is using, or because the ease of use is worth the performance drawbacks.
It really doesn't seem like there is anything you can do. Sure you can talk to your representative, but why are they going to bother dealing with something that such a small margin of their voters care about?
While I agree with you that most if not all sites should offer some sort of no JavaScript fallback, the development resources required to offer such a thing is just generally unpractical when it's such a small minority of users. Government or not, they still have to choose between spending their limited departmental resources on an extremely small minority, or the greater userbase as a whole.
Types, I never could stand them. I started out programming C++ for tiny side projects, eventually moving to python2 for a majority of my projects until I got into a programming class in my highschool and was taught java, and I hated java as soon as I touched it. Java's type system was gross to me, I never really got advanced enough in C++ to use types much and python has no type so I just assumed java was an outlier and types where a stupid addition by it. I continued to believe this even once I got a job in node, until I used typescript. Actually seeing why you would want a static typing system, and being old enough to appreciate the structure they provided changed me, would hardly consider using a dynamically typed language for even a reasonably sized project now.