Indeed, it seems that the problem is not within XForms. However installing XForms brings an actual issue to light all of a sudden.
I have followed up with this specifically in a new topic: ‘AppFramework: Custom template ends up supporting all encounter types (instead of just a single one)’.