This is tough to answer without significantly more details, but I'll do my best to provide some feedback.

I'm not positive what the jar and script do, but at a high level Its likely you need something like what is done with some of the other message brokers (RabbitMQ, Websphere MQ, etc). In order to not manually create all the templates like you mention you would want a modeler plugin and component template. That involved writing a decent chunk of Python code.

That said, your approach of one template per queue, while tedious and manual, should in theory work. Assuming that the script and/or jar file let you pass a queue name as a run time parameter. From what you describe it sounds like DLQ might be some sort of default and you'll need to pass some sort of argument to it.

I wrote a Zenpack some time ago to do what you're asking, but for Websphere MQ instead.  It would probably need some degree of modification for your use, but you should be able to use it for the basic "skeleton" if you like. 

The Zenpack is here:

docs/DOC-12919

Hope this helps,

Joseph