Split the task_type_sub

In a few places it would simplify the logic if we had two types of subs: task_type_sub_self and task_type_sub_pair.

Is there any advantage in having only one single unified type for both kind of behaviours ?

If not, can I make the changes ?