For me the argument for freely releasing components (in a similar way that Acorn did with the nested Wimp, SharedCLib etc) is that it allows software to be written in an easier manner by developers. To me, the Firewall is most certainly not in that category.
I'm curious why you feel the Image File Render module isn't suitable for outside release. Given that it's effectively pointless on the surface to anyone without the Select thumbnailing Filer, no-one's getting anything for free. Similarly, to an end-user SpriteExtend is useless without Select !Paint.
The beauty comes when application developers get their hands on them. Want to write an application to load and render a PNG file? Simple. Suddenly you don't need to use libpng then waste your time writing some custom alpha-transparency plot routines. Similarly existing applications can be quickly updated to support exotic image formats transparently and centrally.
So, to summarise, you receiving benefits from increased application development and additional functionality. Without a large enough user-base to justify development the work wouldn't be caried out without freely available code (as has bene proven by the implementation rates.) All you can really be perturbed about is that others are also receiving some of the benefits.