Most new features such as Capability Inquiry, Profile Configuration, Property Exchange, and Jitter Reduction Timestamp also work over MIDI 1.0 so they can be used when gear is hooked up using legacy serial TRS or DIN connections.
Both MIDI 1.0 as well as MIDI 2.0 are what’s called “transport agnostic”. However, even though sending MIDI 1.0 messages over various transports is well defined, there’s not yet a transport specification for MIDI 2.0!
They have however defined what they call a “Universal Packet Format” which should make specifying transports for MIDI 2.0 relatively straightforward. USB will most likely be the first transport over which you’ll be able to send and receive MIDI 2.0 messages.
Directional TRS or DIN links won’t be suitable as a transport for MIDI 2.0 messages. It’s also expected that most new gear will use MIDI 1.0 transports for a long time to come simply because it offers everything those devices need.