Who knows? Currently there is no one working on a new standard. Maybe an AI will publish one in 2094, hundred years after the first standard.

For now with CL we can program in the past and reuse some code from 30 years ago. Changes will need to reflected in implementations, libraries and community standards. Some stuff would need changing the existing, others not so much. Example: Due to meta-programmability something like the Common Lisp Object System was implemented 95% in the language itself - the remaining 5% largely needed to be implementation specific things like changing the type system. Other stuff like 'threading' or 'foreign function interface' would need more work - but they exist already in implementations and libraries.

I would suggest that this is what Racket is

they don't call it Lisp because it came from Scheme but they wisely realized the first step to making changes is to stop calling it Scheme otherwise purists will just rain fire on it and insist on living in the past

from a practical perspective it seems perfectly safe and reasonable to say Racket is Lisp2023

otherwise maybe elisp? it is by far the most important thing with "lisp" in its name in 2023