It looks like its just power management coming into play. It's not unusual if for some reason the overall SNR/m changes, then power management can increase the gain in a channel to maintain connectivity by ensuring that there is sufficient total SNR to support the overall bit-load.
Increasing the gain is a normal part of the
bitswap process which has an inbuilt allowance for these type of circumstances.
Adjusting the power level in U2 to maintain the overall bit rate is quite logical, as they are the tones most likely to be marked out of service due to bitswap because they are higher frequency and more susceptible to noise. Although it should be said that the process can ramp up the power in whatever channel it is needed most as long as it doesn't exceed the overall maximum power level.
If you look at the 2nd graph which is more magnified, you can quite clearly see that at around 08:50ish SNRM dipped across all channels. Very shortly after SNRM rose in U2 indicating that either there was a miraculous recovery in U2 only or that the power was ramped up for U2. The latter is the most likely in your case because it rose above its normal level.
In circumstances such as the above, unless it's service affecting and/or you are getting lots of errors it's best just letting the modem do it's thing. A resync when some of the tones are below 6dB would likely mean you get a lower sync speed as a fresh sync won't have the benefit of the power gain. Yes you will recover tones that may have previously been marked as unusable, but they will not be able to load as many bits as at the time of your last sync.
It's difficult to say with certainty on a line which usually has natural surplus, but the fact that at one point U0 was running at an average of ~5.5dB then you may not quite have got 10Mbps.
What caused the original dip in SNRM I have no idea, although judging from recovery in the other channels whatever was causing the noise appears to be abating, so it should be now safe to resync to get a fresh bit allocation table.