Yes. The scope of the proposal is well-defined and a change to the syntax was intentionally put in the Future Directions section, because it needs its own pitch and proposal where we can have a more in-depth discussion about other accessors and implicit arguments. This proposal is purely about semantics and changes to the syntax are clearly out of scope.
I don't know when the Core Team plans to run a review for this, but if at the end of the review they decide that we must make the deprecation now, then I can update the implementation to do so (it would only requires a few trivial changes). However, it's not something that I am officially proposing, so I would leave the decision to them. If someone wants to discuss the syntax changes further (and take it forward) then I encourage them to create a new pitch thread.