Yes, this is a nice feature.
How do you plan to use it? As long as there is a connection, you get the current time. When there is no connection, these variables are not changed. Perhaps the library should synchronize the time itself, without additional elements. What do you think?

More thoughts on this topic....

Anyone using an RTC in their project has to initialise it, usually by downloading a temporary sketch to do so.  Once initialised, the RTC is left on its own to deliver what it thinks is accurate timing. We all know they drift somewhat...

If you had an object RTC that can deliver YY MM DD Hr Mn Sc as 6 bytes from the GUI, we could use the rising edge of the "Connect Flag" to update our hardware (or even software) clocks, making the initialisation process redundant. Every successful connection re-synchronises our local timing ...

Since the date/time is already display on the GUI, the RTC data could be a hidden object, like the "sound" object, but would be available in the output variables if configured in the GUI, which it doesn't need to be like any other object.

It is assumed that the mcu has to connect to the app regularly in order to achieve this.  Local (mcu) timing without an RTC could drift dramatically, connecting the phone app would update any local timing parameters.

From the phone to the mcu would be the only point of reference without the hardware having a RTC module

A new object "Time/Date" with configurable output variables to the sketch (include only the ones you need).

The time and date data would come from the phone.