Really, it's the same concept
record the MIDI click to Audio .. use it when you want and how you want.

Or route that one MIDI track to the internal Coyote WT synth, but that's more complicated when you already get the MIDI/Audio concept.
Lots of ways to do it, but I, personally, usually go ahead and make the click an Audio track (like the others).

What this does is allow lots of options moving forward .. mute when you want, or run it thru PGPeakLimit to make it really loud (example while recording live drums) ..
I remember one session where the drummer kept complaining he couldn't hear the click, he needed it louder, and saying "why can't you get it louder?!" .. so I compressed the snot out of it and sent it to just his headphones.

/And then giggled when he ripped his headphones off his head and apologized.
//Apparently I had now got it TOO loud.
///there's no pleasing some drummers

As far as a template, I have a file called click.mid
It is a MIDI file of nothing but click track for 100 bars.
On a new project I open that file, use the flexibility of MIDI to adjust the Tempo to what I need, then render it to Audio. (Save As .SEQ format)
For me it just makes the whole work flow easier when everything is Audio.
Keep the MIDI in case you need it (MIDI adds very little file size etc., so why not keep it)
But after that I mute it and use the Audio click

YMMV

I do not work here, but the benefits are still awesome
Make your sound your own!