I don’t believe this pattern is supported: the problem here is that the boundary event deletes the subprocess, but you’re asking the user task to be created within that subprocess context.
If you want to model this use case, you can simply add the user task (and other tasks) after the boundary cancel event.