Placing a scope on "Create Incident" applies restrictions to both "New Ticket" creation as well as "Service Catalog" requests. Having the ability to scope these two types of Incident separately would be very useful. For example, our org wanted to scope "New Ticket" categories to those related to IT concerns. Other departments would use "Service Catalog" forms to gather much more detail from the end user. We cannot scope Categories for one without restricting their use on the other. This has led to the use of backend automation rules with regex queries to recategorize Service Catalog incidents from a generic "Do not use" category to their proper, hidden from the end user, category after submission. All of which can be avoided if these two could be separately scoped.
