I have what one could consider an "irregularity" in a Drupal module. I have this unique case (mostly due to vendor inconsistencies and ever-changing requirements) where when a user requests a certain item (in this case, something from an inventory database), a hook_menu() call routes them to a callback that polls the inventory API (a REST service), and we pass that REST data to the user through a theme call in Drupal. Attempts to actually display the data directly to the browser are mostly unsuccessful due to CORS issues, and nobody is answering the phone at the vendor.
I've been informed there are some additional requirements that require our newly minted psuedo-content to host a "Comments" section, which if my knowledge of the CMS is clear, only associates with items the system is storing, e.g Entities and Nodes. Before I ask about a definitive solution, I should ask, if there is any way to convince the CMS otherwise, and track a comments record for this faux-content, or if my only option is to save this data as a node (even if its just a single field), and then 301 Redirect to it once saved. Any thoughts? I know this is a rather abstract question with an equally abstract solution, but time constraints make longer-term solutions unobtainable for now.