James has very good point that using wider gamut color space has still benefits for post-production (regardless of output, if the output is wide gamut, the benefits will stay visible, if the output will be in lower gamut, than there is "theoretical" benefit in higher fidelity of color transition, but in many practical tests done of this (not by me) this was almost never proved sufficiently which basically discards for example super high gamut ProPhoto as only being 'halo' space, perfect on paper definition but not leading to actual improvements even for severe color transitions post-production).
I didn't mention it since the OP's client's purpose was for having the wide gamut (CMYK>sRGB) on input texture maintained correctly from conception to print and that currently can't be done.
You want your value output unchanged. That's what 'assign profile' is for. It doesn't change your values at all, it just *displays* colors within the specified profile gamut.
You don't want this at all, I didn't make any mistake with "convert to AdobeRGB", it does convert values to closest resembling, the practical difference of converting to higher gamut space is minimal and we don't want those colors to visually change at all.
If you assign the space, you will interpret those color differently than they were stored at,
which is currently sRGB from Corona or 3dsMax (3dsMax does all the saving from framebuffer, doesn't matter which).
You might be pre-press guy but you still got the point of this thread wrong so don't go accusing anyone that your head hurts from reading their post.
What James wrote is correct also.
If you just want to convert a document to Adobe space just go to Edit > Convert to Profile (never Edit > Assign Profile). But its better to convert from higher profiles to lower ones eg. Prophoto > Adobe > sRGB as you gain nothing from converting up. But the file will be in that color space regardless (as what Juarj explained)
And here is where your reading comprehension fails Pokoy.
The bigger problem here is the first conversion from CMYK to RGB, because CMYK has a smaller gamut for most color tones
CMYK doesn't fall neatly in extremities compared to RGB models (since it's substractive) but it better converts to AdobeRGB (which fully covers it) than sRGB, hence OP's client's request for pre-print files.
His client don't care about the gamut per se, they want exact representation of their original colors, which were selected in CMYK, to be represented correctly in final result. But this will be butchered in first step of input in 3dsMax as the bitmap loader.
So if OP could maintain his whole pipeline in AdobeRGB, everything would work. He could go and do so right now with Vray in Maya for this job. But not for Corona in 3dsMax.
This thread had literally nothing to do with pre-press preparation but maintenance of fully managed color pipeline, but you still had to come and claim to be the smartest. Every time Pokoy, I will ignore these color threads in future, there is no point.