Yes there are some Secure Shell modules that do provide some multi-server operations. However, many of these modules can be difficult to compile on various platforms, require extensive modules like the crypt-style modules, only address parallel operations when running the remote command, do not easily account for hung Secure Shell sessions, etc... Moreover, what about pre and post processing of the information? Such post processing cases, all information in returned to the central point of execution and typically become single threaded--loss of efficiency. Respectfully this may be what you want, or you can have each thread perform its portion of the post process as part of its responsibility. Expand this thought to pre processing, what about checking if the server is pingable or if the name provided is in DNS? These are just a couple of examples of typical issues at hand.
The example provided accounts for a more robust solution, which allows for one to extend to suit their design goals. Also, this solution can easily be extended to Secure Copy, as this would just be another command to run.
Finally if you look at the 'SSH_OPT' which I have defined, these options can also be used with in shell-based scripts, as an alias in the user environment, etc... Such options should almost always be used with a batch style Secure Shell script. It accounts for connectivity time out, known_host issues, remote agent death, and more.