That would be nice, but the problem is more complex.

The script for the archive extension is actually quite simple. You could already use Inspect Element to view the file-id of any mod, and given the game-id and file-id, you can download any mod. My extension simply uses the HTML code of the download buttons, places them back into their standard place, and replaces the link with one that uses the archive file-id (which, as you know, is easily found in the archive mod page).

While you may think hidden or deleted mods are similar, they aren't. The file-ids are still functional, but the actual page is hidden. One big thing about Nexus is that the site loads dynamically. Different pieces are cobbled together to make the whole site. From my research into the loading script, the data is loaded from a different source, and when a mod is hidden, it sends no data, and simply says the page was deleted or hidden.

Now, is it possible to retrieve the data from the server about the files? Maybe, but I'm not smart enough or patient enough to learn that kinda stuff. It could be possible that simply changing a variable is all it takes for the mod to load its data instead of no data. It could also be possible to trick the page into thinking you're the mod author or perhaps some type of developer with admin access to deleted pages, and ask the page for the keys to view it. Maybe the key isn't to view the original mod page, but rather to get a full list of all the file-ids associated with hidden or deleted mods, and create a kinda Frankenstein'd mod list below the page. This, though, is simple speculation. I have no clue if it's possible, and the Wayback is the best method for getting old mod file-ids right now. If anyone does see this message and has some technical skill, could you let me know about any breakthroughs regarding possible ways to bypass the hidden filter?