Thanks for reporting this issue.
We suspect this won't impact users in any practical way. We are currently investigating a more holistic solution for handling deprecation, obsolescence, and versioning of nodes.
We do not intend to address this issue directly, but instead as part of a more comprehensive review.
Thanks.