Currently, parameterization for task name in a taskflow is not supported. Please feel free to open a support ticket to open a feature request for the same.
If you are referring data synchronization task name ,Please follow the workaround :
Step 1: Create a script to call DSS using RunaJobUtility and pass the job name through the script.
Step 2: call the script through command task step in taskflow and pass the job names with the similar design with catch fault which is shown above.
This will help in avoid creating 200 + configurations.
How to use run a job CLI utility :
Also as an alternative .Instead of using the data synch task use a mapping and define the common business rules in the expression (you can parameterize this as well) . and parameterize the connections .In this way you will be able to execute the mapping for various scenarios and at mapping task level set up the email triggers which will help in triggering the email as well.
You can dynamic the way as well. while passing it through taskflow.
How to update connections using REST API .
Fully parametrized option :