what I was getting at is that a smaller footprint also means fewer dependencies, which in turns means less stuff running less and fewer configuration headaches. for instance, if your app requires the full .NET 3.0/3.5 run-time versus just the client profile, you need to include a handful of components for Windows Process Activation. These include additional windows services. If your app requires WMI, then that's yet another set of dependencies that needs to be running. And all these include additional downstream dependencies, etc., etc.
So something that may seem a small thing by a 3rd-party developer can seriously impact what we're trying to accomplish. Of course, you're in a better position in that you can just jump into OpenMobile and make any changes necessary if they're worth the effort.