One of the advantages of doing this seemingly weird projection is that you can treat "local" maps (for some definition of local) as flat rectangular grids without introducing a lot of errors: drawing straight lines between two points, measuring the distance / angle between them, etc., just by dealing with a flat piece of paper. VERY convenient, but the farther you are from the center of the projection, the higher the errors that are introduced.
I can confirm this: I downloaded the old version of the app (on a Windows laptop), isolated it so that it would not auto-update, and then used it to download all my books (after the deadline had passed) and convert them with Calibre, which got rid of the DRM crap. You have to do both the downloading and the conversion on the same computer -- other than that, it worked perfectly for my more than 100 books.
Recently, I used Zig to write a utility that runs on my NAS (ARM-based) and trawls through all directories looking for SRT subtitle files; it then cleans up these files, getting rid of any subtitles that match any of a set of patterns (such as "Please suscribe to XXX"). The utility does almost zero work for already-scrubbed subtitles, and only does work for new subtitles.
Some 30 years ago, I reverse-engineered the format of Prince of Persia's save files and wrote a little C program that would create a save file for any place / level in the game. Just because I could...
I personally disagree. I don't see any poisoning in the original bug report; furthermore, I think it conveys the issue (and some of its subtleties, such as referencing "modern CPUs") much more clearly than the version you propose.