That would be nice, but for most of its uses, you don't want it running over the network. Consider upower or udisks, for example, which control inherently local operations. It's not as though they replace something network-transparent, either. If you want to operate on a machine, run the application on that machine (which you can do with ssh). X-over-ssh is really a different thing, as it's about allowing interaction with graphical applications on a remote machine, the same way normal SSH works for console programs.
In the case of printerd, I think it's meant to be a purely local printing framework. If you want a print server, run Cups. Or Samba. printerd can then make use of either of those servers, but applications only talk directly to the local printerd (in the same way they might talk directly to a local character device in /dev, say).
And the announcement does suggest that there will be an IPP interface along soon, which is the right way to do printing over the network, really.