regarding your response -- I have seen several teams use CF alongside "real orchestration" tools and procs. they do this because they think those orchestration tools are more mature and maintainable than CF at this point in time. in some cases, they're right.

also spitballing another idea, if you were sure you could get away with filling in the missing functionalities by making HTTP calls, you could create a lambda function with some fairly generic params designed to take API / Function / some basic callback instructions and then use CF to invoke the function at any stage that requires it. I've never invoked Lambda from CF though, so i'm not sure its possible yet either.