Sorry, I was focused on how to get the query view in your module working. To have an R report in the module associated with a subset of a table/query, my suggestion would be to add a SQL query to your module and attach the report to that (instead of using a query view).

I have attached a zip archive with the contents of a test module that I created locally that has a study_pubinfo SQL query and R report. When added to the server and the module is enabled, I get the R report to display in the views menu for the study_pubinfo query (note: not the study_pubmed table). Also note that my query and report are attached to the "immport" schema, but the server you are working with likely still refers to this schema as "hipcdb".

Does that fit with your use case?
-Cory