1a.) The "Options" sub-types we use are not shared and have no other content, they not used for anything except as sub-families for this explicit purpose, so they will work consistently within a project, and the end-user will not have those sub families nor need them in a project.
1b.) If the end-user purges one of our equipment families then they may lose lots of information necessary to make the family work; as a manufacturer, we cannot support models that have been modified in any way by the end-user.
2) Again, I keep the "Option" sub-types specific to options, so that no other sub-families of those types are inserted. As a "standard" all sub-families of our equipment should be generic; only the top-level family needs the Family Category specified.