The kitz interleaving info is interesting, but it states that a depth of 0 means interleaving is off. I don't know what "off" means, as it is apparently different to fast path (the increase in latency shows that). And if it is "off", then I don't see how it would help the connection.
In very simplistic terms, there are two paths that DSL can use to transmit data over, think of them as channels.
The Interleaved path can apply interleaving. Fast path cant. However you can send data over the interleaved path, but if you set it to 0 or 1 then no interleaving is applied because there is no chopping up or re-arranging of data.
So back to channels. When it came to paths, BT used to reserve fast path for TV (the old BT vision) whilst all 'normal' internet data was sent over the interleaved path. Some of those with the old BTvision may recall how 500 kbps of their bandwidth was semi reserved for TV and they had 2 IPprofiles. TV performs very badly with interleaving, so this is why they split how data could be sent. Yet the beauty of the interleaved path is you can still use this channel and make it perform like fast path by setting interleave to 0/1.
As eric says:-
Interleave depth isn't the only determinant for latency. It's quite possible to be on fastpath and still have high latency.
BTw can also apply RS encoding without Interleaving. We have seen them do this before (mostly upstream vdsl), however if you arent recording any FEC then it is unlikely.
I think if I were you I'd ask Plusnet to run a
GEA Service Test / WOOSH test to get your DLM profile. That way you'd have more information on what was going on.