Just a view from an 'outsider' who's a user first and foremost.
IMO, SexScripts is fantastic and is fast surpassing CM in terms of flexibility already. It's not as easy to code for, but it makes up for this in using a 'real' scripting language that means not having to learn a single-use one (i.e. spending years learning to script in a code that only works with a program that gets discontinued!).
The thing CM did better (currently), IMO, was being a 'virtual Mistress/Master'. The menu system with choices to ask permissions, confess things, get punishments, see your Mistress/Master's mood, etc. was all really cool, and something that doesn't (yet) translate easily to SexScripts, which seems better designed to handle the equivalent of CM's 'routines'. While this is actually the main reason I used CM (one-shot scenarios rather than as a 24/7 virtual dominant, which was the original intent of the program), I know several folks who liked that aspect a lot.
If anybody else is really keen to make a CM replacement besides SexScripts, my humble request and suggestion would be to focus on the 'virtual dominant' side of things, and leave the 'scenario script' type of thing more to SS, which it already handles pretty well (aside from the whole 'difficult to handle block scripting' issue that so many CM writers are used to).
It would be a sad waste of time if several people were working on multiple, different 'competing' programs (especially since these are all, and IMO should be, free software anyway) when they could be all pooling their resources and skills into making one *really* good program together.
I think CM set the bar for the whole 'virtual dominant' concept (over predecessors like PCM, etc.) and there is definitely a case to be made for an even better successor to that crown, be it SS or another program.
But for creating 'standalone' routines/scripts/games/teases, I think SS is fantastic and I can't wait to see how it continues to develop, and would encourage anyone with ideas and talent to contact Doti and look at working together with him on this.
Just my two cents, from someone who just uses these programs, occasionally writes for them, and who's seen the 'problems' of CM and other programs in the past.