The only XP shutdown-resiliency options I can think of is it make sure that drive caching is as tight as possible. Open Device Manager and find your hard disks. Double click and then look at the Policies tab. There are a variety of options there about caching - disable as much as possible.
Then the next aspect is that powering off doesn't clear the "dirty disk" bit on the disks, so on restart you'll get the "Windows didn't shut down properly" screen with the safe mode options etc. It may be possible to disable the check for the dirty disk shutdown - I recall helping a friend who had a bug on Windows7 where it was reporting all shutdowns as dirty. Maybe google for something along the lines of "disable dirty disk check windows xp" or "disable dirty disk shutdown windows xp". There were some reghacks available to him but this was Win7.
I'll have a think to see if I can come up with anything better. I don't think your problem is going to be related to losing data (NTFS is a transactional file system, but you won't be writing anyway), it's going to be about stopping WinXP having a cow each time you power up. You may be able to set the timeout for the "Windows didn't shut down cleanly last time" screen so it defaults to something like 1 second and then boots as normal.
cheers
tim
ps Just had another thought - what about building a normal XP system then using something like Linux's grub as the bootloader - that may get around the WinXP check for dirty shutdowns. I'll have a thought exercise on this and see if I can come up with something useful.
pps Shame you're not using an old SCSI disk which had an actual write-protect jumper. They were very cool for doing naughty things on old Sun gear - no logs as the disk was physically blocked from writing
ppps The above just reminded me - I don't know what the state of SDL Mame is, but if it's halfway decent you could go for a Linux system and just mount the filesystem read-only. That way you know you're not going to trash anything. I'm not 100% sure that you can have the / (root) partition as read-only, cos things like mtab need updating on boot, but you can probably emulate a live-cd style setup where your "write" disk is actually a ram disk so it doesn't matter that you lose it all with a dirty shutdown as the data never gets recorded. I'd have a look at building live-cd's