Some of the logic in the form rule controlling which fields can be in the same profile (function formRuleSubType) is broken

While adding a form rule to prevent multiple primary fields of the same communication type I also found a bug due to an incorrect syntax in the form rule section of CRM_UF_Form_Field.php. The $errors parameter is missing an ampersand so that the errors it throws are not passed back up to the main form rule.

The bug allows Organization subtype fields such as Teams/sponsors in the sample to be mixed with participant fields among other incorrect field match ups. However if the function is simply "enabled" by adding the ampersand it blocks contact fields such as email from being added to an organization subtype profile.