So, Phillip's suggestion to contact Rustici is a really good one. Privately, they will tell you to contact them first (before contacting the LMS provider), so they can solve problems without a middleman.
(As an aside, if you're in the Nashville area, give them a call and set up an on-site. They're a fantastic group of people; want to hear from not only their customers but also their end users, and listen carefully to what people say about the products that they provide code for. And most importantly, they're willing to, as we say down South, "talk friendly" about the state of the SCORM/Tincan world. Plus, they're delightful peeps.)
That said, it is completely possible to do what you need, albeit requiring a little bit of new code. What needs to happen is modification of either Articulate's crap code or Phillip's excellent code by writing a filter at the module/SCORM API interface. Essentially, you look at every call to the LMS/LRS, then discard anything that you don't want to sent to the server. It's not all that hard if you're at all familiar with PHP; when I had an issue with writing to the SumTotal LMS, I did exactly the same thing except I was tracing the LMS traffic rather than filtering it.
Creative Perspectives, Inc.