I'll have to dig around and see. I'm about 1/3 of the way through reading this thread. Here are some of the design points of the old releases-
folding auto-started with a default configuration and a reconfig script made it easy to reset the username/team and parameters.
prime95, seti, cpuburn, and memtest rounded out the hardware test/DC options.
I used knoppix because it was well-documented how to rebuild it, had persistent home directory, hdd installation script, and LTSP, plus you could choose between a few different DE's/WM's when booting. Its cloopfs compressed about 2GB down to the size of a CD. It was possible back in 2005 to have a pretty complete system with both gnome and kde. Space was a little tight and I did remove a lot of locales, but not all of them.
The important points for most DC clients and their scripts are to make a way to download the latest client if possible. (I made it supplement a built-in copy of the client if it couldn't download it, but distributing most of those programs in the OS may not be legal) I had a way of determining the amount of memory and number of CPU's, so I could determine the optimal number of instances and parameters to use for various DC clients. Have it search for a persistent home and if it finds one, the dc scripts should check for their existence there and use that if its present before setting up fresh work directories in the ramdisk.
Wine was included, and so was an alternative folding script that used the windows client. At the time there were some folding client performance differences not in favor of Linux for some work unit types.
I can get in contact with overdoze, my co-developer, for the LTSP part of it. He'd made his own scripts for running it as a server for diskless clients, although I might be able to dig those up as well.