No, at the moment the process will start but no task is generated, maybe there is another problem with identityservice or ldap integration.
But if it should catch the error event then great. I read on the userguide that "Defining a boundary error event makes most sense on an embedded subprocess, or a call activity, as a subprocess creates a scope for all activities inside the subprocess. Errors are thrown by error end events. Such an error will propagate its parent scopes upwards until a scope is found on which a boundary error event is defined that matches the error event definition"