I don't see any reason why you shoud not apply your valid fixes now.
Well, validity is in question here. Patches were only partially applied by the author, and although I asked for the reason - I have never received a reply, so I can only guess that there was something that the author didn't like. Without deeper understanding I can not defend these patches, only PilotLogic could do that (but that is hardly going to happen). I was hoping for the author to fix all compilation issues, but I am still puzzled with only partial fixes appliance without any feedback to reveal the mystery. That is the reason why I am not for changing CCR WST by myself, to avoid more mess. OPM already provides patched WST (I think that GetMem has applied all mentioned CT patches based on my DIFF files, but I use CT version so I would not know that for sure). OPM version is probably fine, and I am only advocating (a little) for CT version that I could host on ct4laz repo to avoid repatching when new version emerges.
Do you have the commit rights for CCR?
No, and because of the reasons already described I would not like to patch WST on CCR by my self. Regarding CCR, the first thing I would like to see is to completely delete MultiLog and LuiControls from CCR files, or leave only 1 readme file that would point users to author GIT repos which are maintained, unlike 11 year old files at CCR. That is pretty embarrassing for both components and CCR, and probably the case with some other CCR files. For MultiLog I know personally because I was involved in helping author making it thread safe (file logging), and implementing a TMemoChannel so several threads can write to gui Memo in a thread safe way. I have an impression that nothing of this will ever get into CCR, and even if it did it would be outdated soon, so I see no point to have it in CCR. Especially since they can be found in OPM now.
https://github.com/blikblum/multiloghttps://github.com/blikblum/luipack