I would say dont make comments like :-
<snip>
Unless you really know what goes on at the lower level.
That's fine then, I have your permisssion to make those comments! (FWIW.) (My 62 processes include one for MySQL, a handful for SQL Server, several for stuff that it's helpful to have running on a server operating system but which most people won't have on a workstation version, an inordinate number to drive my HP printer but they never were any good at software, a copy of squid and maybe one or two other things I installed a year or two ago for a specific project and haven't used since. But as all these things sit there consuming no CPU cycles and no real memory until such time as a request is made to them they make no contribution to the machine being slow, do they. And it isn't.)
Writing a true windows service is not trivial as the interaction with SCM can be quite complex - I have written a few and it takes a long time to sort out the interaction with the operating system before you even get around to sorting out what the service is meant to be doing.
It's essentially boilerplate code though, it doesn't really matter that much whether you cut-and-paste it into your own application or use the pre-packaged version in svchost. Except that writing a "proper" service and giving it a recognisably useful name might reduce the chance of some numpty killing it via task manager and then wondering why their computer doesn't work any more!