You're confused. It's true that the AGPL only applies to modifications, but programs that link to (A)GPL libraries are considered modified versions of those libraries for purposes of the GPL. So if you link to an AGPL'd JSON library and use it throughout your website's source code, your website is a modified version of that product.
And as for your workaround, here is the text of the AGPL:
>your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software
You setting up a reverse proxy doesn't mean that users suddenly aren't "interacting with" the program. By the same logic, they aren't interacting with your program even without a reverse proxy, because they are actually interacting with their own computer, their own operating system, their own keyboard. No court would accept such a pedantic and useless definition of "interacting with" because it's clearly not what the contracting parties intended. Contracts terms are given their reasonable meaning, not unreasonable meanings.
You also complain about e.g. MIDI not having a way of sharing source code. Here, you're again misreading the license. The license requires that "providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software".
Notice what it doesn't say. It doesn't say it has to be offered over the exact same protocol. It just says you to offer it from A network server, through SOME standard or customary means. The license even goes onto say:
"If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source. For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code. There are MANY WAYS you could offer source, and DIFFERENT SOLUTIONS will be better for DIFFERENT PROGRAMS; see section 13 for the specific requirements."
It's true that earlier it says you must "prominently offer all users users interacting with it remotely through a computer network" an opportunity to receive the source. But in cases where the protocol literally has no way of embedding that information, then there's no reason to think you can't fulfill this requirement by, e.g., prominently including a link to the source code wherever you advertise or document the network service.