I think it's best to create scope for every condition even if it is used only once. I like that a name is given to the conditions so it documents what condition represents. It also promotes DRY. 

When a developer later comes and needs the same condition, he'll just use the scope. Or he combine some scopes to get what he needs (or maybe he adds a scope and combines it with existing ones.) On the other hand if the condition is not amongst the scopes a developer may create one (which would be best) or he just writes a condition, I do not believe he'll check whole code if the same condition is already somewhere, and duplication begins. This is why I would add a scope.

On the other hand, I do not fully understand the context here, if it's a special case and it's highly unlikely that this will be ever needed elsewhere than the reasons for scope are significantly weakened and It is not worth it to create another PR.