I've just gone through this on one of my lines, it's 56db and used to be fine on 20cn at 4500-4900 sync. I moved to 21CN and got sync capped to 2272. I got forced down the SFI engineer path to resolve it. He came, rang up some power that be who quoted 11 retrains and stuff but reset it anyway as I explained to the engineer that was me jumping through hoops reporting the fault being asked to reboot routers changed routers and provide screen shots etc. My line failed an asp? test or something with B-E low insulation or something? (was bottom on the list of the test) but it was Friday afternoon and he said he was only allotted an hour and said I would need a new engineer scheduled as his modem wasn't 21CN compatible. So the engineer went I had 4992 sync on adsl1 so left it at that rather than mess with settings. a few hours later I lost sync for 3 days over the bank holiday weekend. faults wouldn't say anything other than we can't chase it as there is an open fault. Line comes back fine for a few hours then it dropped me to 4544, then at 4am it drops me right down to 3072 with a capped sync and 19db snr. My isp arranged another engineer visit (but had down the other was a no show for some reason).
This engineer was completely different and seemed much more willing to fix my problem. He also said his modem wasn't compatible with 21CN but rang some power that be, got 3072 sync limit confirmed and removed checked all the boxes and by some miracle changed my B-E pair? for a new one and its 44db

the 1st 24 hours I had 24000 crc errors so I expected a dramatic drop but interleave got switched back on by DLM (engineer had it turned off to do with his modem) and crc errors have dropped hugely and sync gone up to 7611.
The bit that got me was the resulting phone call between engineer and powers that be. The engineer queried the (I assume its bt wholesale or someone on the other end's) notes that my line had 72db loss when it was actually 56, so he updated the records to show the new 44db but said he could still see line errors(crc's I assume) but it was left to see how DLM decided. So far touch wood it's not bitten again.
My observations going through this is that bt have this data possibly for more than just the availability database and the engineers concern over these figures makes me wonder if that database governs to some extent the aggressiveness of DLM as I had much less crc errors before and got limited. The DLM seems to count sync events and data errors (CRC and corrected if the DLM is aggressive enough) and is much more diverse and happy to provide what is stable in its eyes, it doesn't seem to care if our lines were stable for years at 4500 etc

I used to tweak SNR in the past and now I have to say I'm almost afraid to even reboot the damned router through fear of DLM shouting fault! and limiting me again. I guess I'm lucky in some ways as there was a fault showing. I'd love to see what a more knowledgeable person had to say about the new DLM and the things it considers before capping a line. The second time my line was limited it was in 1 huge step it didn't even try snr limits.
I know I haven't helped posting this, I just wanted to share what I could glean from my experience of the frustration of DLM on 21CN. And advise anyone who tweaked to get higher sync on 20CN to think very carefully on 21CN.
sorry if I rambled

Dave