If it’s based on task type then you can right now create new work template where you replace "task[name]" with "task[type]" and add filter to use the template in project_settings/global/tools/Workfiles/workfile_template_profiles. But I expect it is not type based?
Also if you don’t care that all workfiles are in same folder then you can just remove task[name] from directory template so you can see all workfiels from all tasks in workfiles tool.
I can imagine that task on asset would have something like a "group" same way like have "type" right now that could be used in templates. It should definetely not override "name" but the code should check if group of task is filled and if not then use task name instead. In that case you can use task[group] and task[name] in templates at the same time which gives more abilities when needed. For example directory template can have task[group] but filename can have task[name] so you can see workfiles from different task in workfiles tool but use different versioning for different task name.
In all cases the question is where and how to set the thing I’ve called “group”. I don’t think using ftrack links solve what is the source name (or does?) that should be used in templates. It can easily cause accidental change of the group value during production.