The only logical reason I can see to use the Matrix with hardware is if one had modules; i.e., no keys or pads.   That seems like a reasonable thing to do since those sounds have to be triggered by external means.  And, the Matrix allows entire clips to be triggered at one time, not to mention multiple clips/synths per column, something that'd be difficult to do using the PRV or SS.   At least in real time, aka, as a performance.
 
But I stand by what I originally wrote - if someone with tight finances purchases a product without confirming whether that product does the one and only thing they want it to do, well...   Assuming that all of this took place after X2 was already released, of course.
 

Matrix works great if you have a touchscreen that accepts multi touch. Seth demonstrated it quite nicely. 
 

John
P5 didn't work with hardware if I recall. So I don't get the connection that the version in Sonar should. 

cakewalk received so many complaints from P5 users that as Mr. Brock pointed out in the 5th post on this thread "The difference is that Rene Ceballos quickly cobbled together a fix in the MIDIOut plugin. "

stevec
The only logical reason I can see to use the Matrix with hardware is if one had modules; i.e., no keys or pads.   That seems like a reasonable thing to do since those sounds have to be triggered by external means.  And, the Matrix allows entire clips to be triggered at one time, not to mention multiple clips/synths per column, something that'd be difficult to do using the PRV or SS.   At least in real time, aka, as a performance.
 
But I stand by what I originally wrote - if someone with tight finances purchases a product without confirming whether that product does the one and only thing they want it to do, well...   Assuming that all of this took place after X2 was already released, of course.
 

I first reported the "Matrix can't send MIDI to hardware" bug when the Matrix first appeared, whichever Sonar version that was. To get the response from Cake that it could. Then, after some toing-and-froing they agreed it couldn't and the bug was listed as passed to the developers. Had the OP asked Cake they may well have got the same response I did initially. Several Sonar updates later the Matrix was finally de-bugged in this respect.
 
I have keyboards and pads and use hardware synths. I generally record the MIDI quite a time before the synth's audio. Several reasons. MIDI is easer to edit than audio. I only have two hands and smetimes I want to tweak the synth in a way that would require three or more hands if I was playing it at the same time. I may decide at some point as a project develops that the MIDI side of things is fine, but I need to completely re-design the synth patch. I might record a chunk of  MIDI and loop it.
 
I very much doubt I'm the only person who works like this either.
 
The Matrix is simply another window into Sonar, just like the track window. You may as well say that the only people who need MIDI tracks, the piano roll, the step sequencer, the event viewer etc. are people who lack keys or pads so need a way to trigger MIDI in another way because those with keys and pads just play the synth and record the audio output. Me, if the track view, PRV, Step Sequence etc. can all send MIDI to hardware, then I'd anticipate that the Matrix View can as well. Why would I expect any different?

However, I do agree that the OP is probably best taking their complaint up with Cakewalk directly.