yes that was I was targetting
(note that cmd does read input, so it's not the actual use-case, but more a CUI program behaving like "start /exec" but without the termination of child if parent terminates)
what could be misleading at some point is that depending on whether conhost's input thread is started or not we may end up with different behaviors on ctrl-c (apps that way be killed are not exactly the same). But that's pretty theoritical at this point.
but we can sure wait for reports on this area (if any <g>) to more forward.
preparing a simplified version of this MR