This feature is already planned. It's currently schedule for 3.1.0, but is subject to change.

It's scheduled for 4.1.0. It's a low priority feature at this time as we've more pressing issues to deal with (primarily fixing bugs first and foremost). I've no idea when it'll be implemented exactly, sorry.

With flexibility comes complexity. I don't know what to tell you. The more features we add the more parameters there are and the more complex it becomes. You're asking for another parameter, which just adds to the existing complexity. That's just how it works.

CB Auto Actions is lacking documentation. I've rewritten it for CB 2.x to be significantly easier to use, but when it comes down to it it's just a tool. A tool that already describes it self (every input and every action describes it self with descriptions). Nick has also been working on multiple step by step video tutorials for CB Auto Actions, we also have usecase tutorials for CB Auto Actions on our Tutorials page, and there are numerous usages all over the forums. For CB Auto Actions the tutorials are significantly more valuable than a documentation that just restates what is already next to every input as the tutorials show you actual usages. At any rate a documentation is planned.

Yes, for CBSubs 4.0 features are low priority. This is because we've multiple bugs that need to be fixed before we add more features to it that could just introduce even more bugs. We've internally agreed that a bug fix release followed by a feature release would be the most appropriate strategy.