Yes. You can solo override the MIDI track(s) or the audio tracks, depending on what works best. I usually prefer solo overriding the audio tracks so that room and overhead outputs are always live. If you solo the MIDI tracks, you're going to lose OH and room outputs when you solo the audio track for a kit piece (maybe desirable with something like AD where hats and cymbals are only present in the OH signal).

Alex, one way to make your workflow better is to simply have a thin sliver of Track View visible at the top of a docked Console View, giving you access to the Folder Mute/Solo buttons:
 

 
Save it as a screenset which you aren't currently using.
 

I normally use just one audio track for the whole drum kit for convenience (I use the drum synth's internal mixer and effects) but I've just run a quick test in both Sonar and Studio One, creating separate audio tracks for kick, snare, etc. and, although S1's drum editor is so basic that it can't even solo/mute each drum in the editor or create a hybrid kit from multiple synths, soloing each drum in its console view worked perfectly. Of course, no workarounds such as solo override or track folders or grouping Solo buttons were needed. I wish it was this simple and easy in Sonar as well (the current implementation isn't a show stopper for me, though).

Another easy workaround is to assign the solo button for all of the drums' audio tracks and midi track to a permanent group.
Soloing any one will solo the lot, but in the drum map you can now solo individual kit pieces.

Bristol_Jonesey
Another easy workaround is to assign the solo button for all of the drums' audio tracks and midi track to a permanent group.
Soloing any one will solo the lot, but in the drum map you can now solo individual kit pieces.

 
I've just tried it and, as I expected, soloing the group doesn't work properly in the PRV Track List Pane (I hear nothing when I solo the drum map track in PRV). The same issue has been confirmed by CW: http://forum.cakewalk.com/PRV-Track-Pane-Solo-button-grouping-issue-CWBRN18282-confirmed-by-CW-m2963934.aspx (see post #3 for simplified steps)
 
(edit: The scenario in the thread I pointed to is different from the one discussed here but I believe the cause of the issue is the same)

Jlien X

Bristol_Jonesey
Another easy workaround is to assign the solo button for all of the drums' audio tracks and midi track to a permanent group.
Soloing any one will solo the lot, but in the drum map you can now solo individual kit pieces.

 
I've just tried it and, as I expected, soloing the group doesn't work properly in the PRV Track List Pane (I hear nothing when I solo the drum map track in PRV). The same issue has been confirmed by CW: http://forum.cakewalk.com/PRV-Track-Pane-Solo-button-grouping-issue-CWBRN18282-confirmed-by-CW-m2963934.aspx (see post #3 for simplified steps)
 
(edit: The scenario in the thread I pointed to is different from the one discussed here but I believe the cause of the issue is the same)

Wow - that's as buggy as hell!
 
Sorry, I suggested this before trying it myself, assuming it would work. But it doesn't.

Don't have time to wade through the referenced thread right now so I'm not sure what the exact issue is there, but I can tell you that in general PRV soloing in the drum pane works fine when using solo override on audio output tracks and soloing the MIDI track(s) driving the synth.

@Bristol thanks for the tip...

So, IMO there's currently no "perfect" workaround to this issue. I hope CW will either fix the PRV Track pane bug or make Solo Override unsoloable unless you Shift-click the solo button again. 

It's not a bug it's a feature ! ;)