Correct, and it’s all fine for the sun phases, as they do not change throughout the course of the day
and I correct myself from the original post, in that the Moon Illumination actually also does update every minute.
As the moon phase age (new moon to new moon) does change continually throughout every day I would have expected it to also update every minute, especially as now in OH4 (and possibly already in OH3) the value is being reported as seconds, where previously in OH1/2 it was reported in days. Much the same with the Moon phase name, which can also change through a day, and close to a new moon and full moon can actually have three different states in one day (Depending really on which illumination changes you define for phase changes).
As the moon phase name is generally reported for whole days though, also with other astronomical sites or calculations, I suppose a moon phase name per day can be acceptable, but the Moon Age once a day, and then reported ins seconds, is pretty off.
Exactly my point - easily and poignantly observed yesterday and today.
Yesterday 23:59
Where the moon age was reported as 29 days 32 minutes (from my JS transformation from the initial seconds), with this age being there for 24 hours since 00:00 without any update all day.
Then shortly after midnight Today **
This is 13 hours and 36 minutes before the actual New Moon, so any age of 10 hours and 22 minutes is just completely wrong for what is supposed to be a scientific astronomical binding calculation, even without not updating throughout the day, but already for 1 minutes past midnight on the day of an upcoming New Moon.
Then several hours later today, at 11:10, just over two hours before the actual New Moon it all still looks the same for the Moon Age
Then comes the actual New Moon event at 13:37, when shortly after at 14:05 nobody can really deny that the Moon Age is supposed to start brand new, but what do we get?
Same old 10 hours 22 minutes, which will stay like that until midnight today again.
Even right after midnight this morning this 10 hours 22 minutes age is the actual age of the moon at midnight tonight, so a value in the future, after the actual New Moon event today, but already shown through the whole day, when it is actually totally wrong for 23 hours and 59 minutes of then day 
So the Moon Age is always only correctly reported just after midnight every night, but that’s it. With OH2 and its reporting in days at least this changed to 0 days for the whole day, much the same as the constant Moon Phase name
Sure I can adjust my JS transformation again to only report in days, I just assumed that with the change to the Moon Age being reported in seconds now, that at least this also came with an improvement in accuracy and progressive reporting of the age, but alas, it only seems to be a unit change 
Exactly, I can always see the exact date and time when the next phases will occur, as I have put into my Moon Phases section, but then it just makes me cringe when the above age is so obviously completely wrong when seeing the two sections together.
I surely could, but with the Astro Binding supposedly reporting the age why should I, or anyone else, have to recalculate it just to get a correct result. Should that not be happening with the phase#age already?
Yes, would also work, but again a pretty hacky way of getting a result which, in my opinion, should already be sensibly handled by the Astro Binding.
As I say, I’m just evaluating OH4 to see if and when I might switch over from OH2, and just pointing out my disappointment when first seeing the moon age being reported ins seconds now, but still only disappointedly recalculated once a day just after midnight giving the above shown wrong results.