Thanks Tim.
I'm working with a client that has several different levels of users, with several different work flows, on several different continents, so while I can and will push for RGB files, ideally, or at least CMYK files with profiles, unfortunately there are probably a number of legacy un-profiled CMYK files that will be uploaded as-is once the project gets rolling.
I spent the day on what was mostly a fool's errand, I'm sure -- and went on several time-wasting wild goose chases -- but have made a little progress. I now have it checking for CMYK images on upload and applying a generic CMYK profile before converting to the other sizes in RGB. Not ideal, I bet -- still a slight color shift -- and I know I've only tested a handful of images. But, looking much more acceptable (although I hear you about not knowing even what the target I'm shooting for is -- and properly profiled files is the correct answer, short of RGB source files) -- but at least it's a step or two or three away from the neon images -- which were either caused by unprofiled conversions or simply CMYK files displaying as they do in the browser.
At the moment, though, it all falls apart when you use the Transform plugin to save to RGB formats, though... So, short of someone with a magic bullet, let's see where this goes.
Thanks again,
Stephen