OK, looking at this page: hidden link
I see, checking the source code, that it is not using a custom Toolset archive, and as far as I can see it is not using any Views on the page at all (e.g. in widgets).
So there would be no reason to expect a URL like hidden link which includes parameters from Toolset Views (or custom archives).
"For the ones like this it doesn't make any sense that they would even load, they should be going to a 404 error."
That's not the case, anymore than hidden link should. Unknown parameters are just ignored.
For a URL like hidden link to be crawled by Google, its robot has to have found that same link and followed it.
On pages which *are* custom Toolset archives, then the links come from the archive itself, for pagination.
But for pages which are not, the link could be from some other page on the same site (including an archive), or it could be from the sitemap, or it could even be from an external site. (Failing that, could it be some strange caching issue? Not sure.)
If you haven't already, I'd check that your sitemap looks sensible, if you have one.
Then, for this particular link, if it came from another page on the same site, it makes sense to think it came from whatever page contains the View with ID 884 (or it could be a custom archive with ID 884).
Can you locate that? Does it contain any links to hidden link? (I wondering if the links are malformed in some way, such that the URL parameters for the current page which includes URL parameters for View ID 884 are somehow getting added to the link to the hidden link page.)
It's quite a while since I've used Google Analytics or Search Console, but I think it may be possible for the URLs it reports crawled by its robot to determine the source of the link, i.e. where was the robot when it followed the link in question. If that were possible it should help narrow things down.