I believe today the gains are outweighted by the costs of this technique: memory isn't really the limitation factor anymore. On the other hand, grouping several mostly unrelated services in the same process is a security and stability issue.
TL; DR:
sc config <servicename> type= { own | share }
I got that from this SuperUser stackexchange question:http://superuser.com/questions/860117/isolate-hosted-service...
A registry-tweaking approach is also given.
Then wrote up my own answer to the WU issue:
http://superuser.com/questions/77658/svchost-eating-up-memor...
using a monolithic process is outdated?
using a shared process is outdated?
using threads is outdated?
trying to conserve RAM in this fashion is outdated?
svchost in Windows in particular is outdated?
Starting services on a 'need to run' basis is outdated?
...and quite a few other options. It seems to me like all OSs have similar facilities, so I'm not sure what he means that would not apply to other OSs.
However the biggest problem with 2) is that you cannot see what individual thread(s) cause problems and you cannot easily kill/restart the offending DLL.
What does he mean by that, exactly?