First, writing XSLT IS PROGRAMMING. No matter what the marketing guys say it's just as much programming as, say, writing SQL is.
Second, how's xml in xml in xml in xml that xml the xml to xml the xml xmling until xmlly xmled gonna help in converting the file into a data structure to be used in a program? Do you plan to write a stylesheeet that'd convert he xml into a piece of Perl code you can eval""? Or ... in case the program was supposed to import the data into a database, convert it to a bunch of SQL statements?
This more comprehensive solution is, more often than not, both next to impossible to read and, as soon as you happen to need anything but the very basic transformations, fragile and XSLT processor dependent. Even if both the source and the destination is XML, XSLT gives you little more than just the ability to change the structure. How much can you do with the tag contents or the values of the attributes? How do you fetch data from other sources?
Enoch was right!
Enjoy the last years of Rome.