That is how processes work. As long as a plugin is dynamically loaded into the same process space, it has the potential to crash the host. Apple has thought about this a bit with AUv3, allowing for hosting each plugin in a separate process, in order to protect the host from crashes. But this comes with significant drawbacks - plugins cannot share resources anymore, no common voice pools, allocators, sample RAM, and there is a substantial overhead of interprocess communication. I wouldn't want that in my template.
I have seen scripts bring down Kontakt many times, so you should definitely contact your instrument developer, if you can ascertain that exactly that instrument is responsible. Only NI would be able to debug the crash dumps however. You may refer to me when you contact NI, I would be happy to assist them (Kontakt developers) in case they have questions.
Good luck!