It is possible that their implementation had some other non-audio threads running, possibly running erroneously at high priority. Those would be running all the time, regardless of whether the plugin was in the active rackspace.
We’re seeing quite a few bugs in Kontakt these days — personally I’m staying with Kontakt 6 for live performance use.