Sure, for example in my experience so far (like8++ yrs) there are always some discrepencies between dev, test & prod. Admins tend to change or add choices which makes the condition builder expression invalid if you use such a choice made on dev let say. Also it depends when to who and what email you want to send. You can handle this with standard notifications as you did it, but (at least in the sense of creating and managing these) I prefer using events. If you open the task table (I think incident table have better example) you can find business rules managing exactly that - firing events on a given conditions where more complicated logic is involved. And you can use one BR to handle all of your events with if/if else/else or swith - depending on your requirements.
Not to mention that if your sys_id's are different of your cat items then you are in trouble for sure. To avoid such cases I add my own properties which I just get and use instead of hardcoded values (like if(current.name == gs.getProperty("my_super_incident")) - where my_super_incident is either the sys_id of the cat item or the name - but easily changable via simple property.
