Since IRC is a simple text protocol it would be massively excessive to use XML for something like that. Simply having a line-per command with tokens would make a lot more sense. Also, having a 'service=dalnet' would be a bad idea, basically all it's done is mean the IRC client now has to somehow find out that information from DALnet. Plus, what does this system really provide? It just means there's now an external source to information that can already be obtained as necessary via /*serv help (assuming a service supports the help command, but then again if they didn't support that why would they support more complex external documentation?).
As for the RSS thing well I don't think that should be done by an IRCd. It should be done by a bot, whether that's a services or user bot doesn't matter, but I would suspect that most networks wouldn't really like the idea of processing statistics for any and all channels that requested it, maintaining a database for it all, and then supplying RSS feeds for anyone who requested it. Seems like a drain on network resources as opposed to each channel using their own bot, recording and providing statistics however they want.