I think this has to change and may just be an outdated part of the timeline that hasn't been updated yet. After all, this item is still on the timeline too: "Enterprise policy can let Manifest V2 extensions run on Chrome deployments within an organization." But that doesn't make any sense anymore, because V2 will no longer be disabled on the stable channel in January, so there's not even a need for an enterprise policy to keep V2 extensions running.
It wouldn't make any sense to let V2 extensions keep running until June but disallow updates. What about security issues? They have to allow security updates.
> January 17, 2022: New Manifest V2 extensions will no longer be accepted by the Chrome Web Store. Developers may still push updates to existing Manifest V2 extensions, but no new Manifest V2 items may be submitted.
> January 2023: The Chrome browser will no longer run Manifest V2 extensions. Developers may no longer push updates to existing Manifest V2 extensions.
So V2 would be disabled in the stable channel simultaneously with the end of updates, in January 2023.
Only a special enterprise policy could keep V2 extensions running for a while after that time.
It wouldn't make any sense to let V2 extensions keep running until June but disallow updates. What about security issues? They have to allow security updates.