Well, I've just reflashed a new version, and it's not bad, but not perfect.
I had to cut some corners to get to testing it (wanted to run over the weekend) so I don't have clean OEMs for all these, but in addition to the existing OEMs, I've put mortscript, mortplayer, audacity (great! recorder app, freeware, you need to register to turn it on) and several missing "hack" registries (the usual cache goodies for access, animation off, etc...) in.
I am running into a problem in that some of my reg entries are getting overwritten by later reg entries. There does not seem to be a clean way to make sure that does not happen unless you keep requesting UUIDs until you get a "bigger one"
However, this ROM has about 90% of what I run pre-installed on it, and it uses just 5.6mb internal ram (well, my contacts are a meg of that) leaving a whopping 34 meg free. Program memory after a reset is 17mb used/29mb free, which seems very good.
My take on the OEM thing after working on 10 or so CABs is, if the app is written well, it can be ROMed. If it has hard-coded paths to some \Program Files\foo directory, then there is no benefit to ROMing it - just stick the CAB in your extended_rom or storage card and install it.
Some stuff defies all efforts to OEM - I have the generic_unlock registry entries in the ROM, but on boot the extended_rom is still hidden (yes, it's free of junkware!) so those reg entries need to be re-applied. The Crossbow theme is in ROM, and even pre-selected, but for some reason the background image isn't the crossbow one. Selecting some other theme and then selecting crossbow fixes that.
So, it's not perfect. Any pointers for the above would be welcome.