Well, it’s not enough for you
We don’t want / use max mapping system, instead we use the Blender one with the nodes, it’s true that some Vray nodes are not supported, it’s not perfect, but in my 15 years working with max there has not been a single library model that I used with the incoming material configuration, so in our case, we are doing the same we’ve been doing for years, for us it works.
I could talk also about the things that don’t work in other packages when I try to send Blender scenes to them, but that is not the point of this conversation.
The point is to recommend Cycles to someone because of the reasons I exposed, that does not mean that it’s better or worse, it’s just a preference, in my case based on our needs, in his case the needs may be different so he may prefer RedShift.
Cycles is not my child, RedShift is not an enemy or anything similar, Blender is a tool, Cycles is a tool, RedShift is a tool, don’t look at this conversation as something emotional, it’s not, saving 3000€ / year is good for anyone, working with the main Blender render engine is good (in my perspective) being able to modify it with a dev is also good (in my perspective too) but it is a personal opinion again.
If you don’t agree… that’s good