I actually don't think I understand well enough.....
The high-level overviews are interesting if you plan on writing an entire similar system, or to understand pain points in an existing one you have
This seems valuable as well
I generally just don't know how to grok CS papers well. Thus, I can't say what value I expect to gain, if I'm always gaining zero value.
Wobbrock, J.O., Wilson, A.D. and Li, Y. (2007). Gestures without libraries, toolkits or training: A $1 recognizer for user interface prototypes. http://faculty.washington.edu/wobbrock/pubs/uist-07.01.pdf
They also have a great page related to that paper with actual implementations and links to works building on it: http://depts.washington.edu/madlab/proj/dollar/index.html (Otherwise it can be worthwhile to follow the citation chain on Google Scholar or other sites, at least with papers that are not cited by everybody)
Some other ideas:
There are also resources like https://blog.acolyer.org/ where papers are presented in blog-post form, reading both the paper and the reviews might help to get an eye for what you can and can not get from them.
Try to find conferences or other venues with papers from a field you know a lot about/have worked in, reading papers with understanding for the context is always easier. Many fields have "classic" papers that are often referenced and more or less required background knowledge to judge things, these are interesting to find and read as well.
Question for you: What do you want to implement from such papers, and what do you expect to gain from doing so?
They describe on the one hand small-but-important details and on the other large-scale overviews over really complex systems. The small details are presented precisely enough so that you probably could code them relatively directly, but they aren't necessarily immediately useful. E.g. in the Gorilla paper you probably could implement their compression algorithms from what they've written there. Is that useful to you? Do you have a problem where you can apply that implementation?
The high-level overviews are interesting if you plan on writing an entire similar system, or to understand pain points in an existing one you have, but there of course is a lot of engineering and knowledge involved that is not in the paper.
I'd say papers that do not present a specific algorithm with in- and outputs you can easily deal with using what you have are not good candidates to just go from paper to implementation, and even then the paper without further context often doesn't give you all you need to do so.