Can you not strip the system binaries? This only makes development harder, as it is no longer possible to easily compare binaries with stock 10.6 to see if they are modifed.
Additionally, I believe that development cannot be sustainably done this way. If your goal is to reduce the number of images floating around, then there should be a centralized way (i.e. master AFP server) where developers can update files, and from which images automatically get built from). Otherwise, development will eventually sprawl into a mess of different images based on different images.
I agree to both of the points.
For consistency and transparency in development we need to have a procedure to start from the stock 10.6.8 and arrive to 10.6.8 ppc, reproducibly, and so that all replaced components can either be built from source (if desired) or borrowed from the publicly accessible server (if those are buildable from source), or otherwise borrowed from existing Apple images (10a190, 10.5.8 etc.).
The only exception to this may be patched binaries which @educovas made to fix some issues to make 10.6.8 bootable. Those can be provided “as is”.