For a task that only matters while the VC is displayed, I would agree.
How about this case: A view controller is a child of a tab bar controller. It uses an AsyncSequence-consuming for await in a Task to listen to notifications indicating it should invalidate its data. After the VC receives invalidation from the task, it loads its data again immediately if visible; otherwise it loads when it next appears. Here the notification-observing task needs to outlive visibility but not outlive the view controller. If the whole tab bar controller is modally dismissed, the view controller should not leak.
Avoiding strong self capture is the usual way to solve that kind of thing, but we don't have the compiler's encouragement in this case.