I'm sorry to bust your bubble. But all 32-bits are amazingly light on RAM
until you flesh it out with a current web-browser and then use that web-browser to access current web-sites. IIRC, Jamesbond set up dpup-stretch in a VM and booted to desktop using only 68 Mbs. Experimenting here, viewtopic.php?p=4070#p4070 I was able to boot a 'moderately stripped' version of radky's Busterpup using only 130 Mbs of RAM. The original OOTB version had used all of 137 Mbs of RAM. On today's computers what's 130 Mbs, or for that matter, 137 Mbs of RAM?
But as soon as you open a web-browser capable of accessing today's websites you'll run into figures like these (from the above post):
"...starting palemoon, pup-sysinfo reported
Actual Used RAM: 177 MB Used - (buffers + cached)
Closing that and starting Mike Walsh’s Seamonkey 2.46 portable, viewtopic.php?p=2206#p2206,
pup-sysinfo reported
Actual Used RAM: 151 MB Used - (buffers + cached)
Entering “Cats Images” into a google-search in seamonkey pup-sysinfo reported
Actual Used RAM: 408MB Used - (buffers + cached)" Emphasis supplied.
Unlike Tahrpup, more recent versions of 32-bit Puppys --from xenialpup32 bit on-- do not require installation of gtk3 and other libs; and can run some of MikeWalsh's 'Chrome-clone'-portables, such as iron, vivaldi and slimjet.
Not that tahrpup is a 'bad-puppy'. It just that IMHO for most computers limited to 32-bit operating systems, there may be better.