In order for that to work, the browser would have to actually implement an XSLT engine. I thought they all stopped shipping such engines about 10 years ago.
If you mean postprocessing the feed server-side with an XSLT sheet, to then serve the resulting page: sure, that would work, and a lot of people used to do things like that around 2003. It fell out of fashion because XSLT is just hard to safely combine with advanced JS-based features.
Strange, Chrome and Safari on OSX still render xml with referenced xsl stylesheets just fine (pointing to 192.168.x address). Browsers still have XSLTProcessor accessible in javascript too so I'm guessing they still have XSLT engines.
If you mean postprocessing the feed server-side with an XSLT sheet, to then serve the resulting page: sure, that would work, and a lot of people used to do things like that around 2003. It fell out of fashion because XSLT is just hard to safely combine with advanced JS-based features.