Well it's not up to me it's up to the sysadmin :-).
It's ALOT easier for you to *ask* your sysadmin to set up a virtual interface for a 127.x IP than it is for us to code in ssl/ziplinks. I know for a fact that it is because I just happen to own a hosting company and I give my users a virtual localhost so I know how easy it is and best of all it's free!!
The Anope Team feels ssl/zip is not worth the resources, thus it will not be added. If you want ssl/zip
1> use localhost and "piggy back" the ircd's ssl/zip
2> use stunnel
To be honest, ziplinks for 99.99% of the networks in existence is a waste to time and resources. IRC uses very little bandwidth to start with. Even some of the largest nets in the world only use about 300kbps sustained This is on a 40,000 user network, not the 10, 100, 1000 users that most nets have. 300kbps isn't even enough to saturate my cable modem upstream let alone a properly hosted machine in a data center. Most nets run at less than 5kbps .. absolutely NO reason to zip that!
You have a better chance of your shell account hacked than you have of having an irc server data stream sniffed by the wrong sort of person since sniffers require root access it can't be done locally accept by your system admin. IN the event that it IS you admin, you have bigger problems, not to mention that ssl won't help you at any rate. Unless you force ALL users AND alll servers to connect via ssl, then ssl is a moot point. Yes, services is a server and we have already told you how you can use ssl with services. I have NEVER seen an irc network in the thousands of nets I've visited that ONLY does ssl.
User passwords is the ONLY *real* reason to encrypt data and you have a better chance of all your users accidently exposing their passwords than you being subject to a sniffer. If you are paranoid about password theft:
1> use 100% s2s and 100% s2c connections, no plain text connections on any physical interface.
2> encrypt your users passwords in the db's
3> disable ns/cs sendpass/getpass (automaticly done if you enable #2 above)