AIUI CBTC (of any flavour, be it Thales/Hitachi Seltrac, or Eliz line type Siemens Trainguard, and so on) are more readily intregrated with ETCS while DTG-R was more difficult (or even impractical?). Long term - that is very long term - LU CTBC will have to interface with NR ETCS at some locations. More of a strategic long term plot to not get lumbered with a system that was more difficult/costly to interface.
If one considers the difficulties there were with getting all the different kits for different section to work on 345s, you'd want to head similar issues off. Down at the level of track to train bits and bytes, CBTC and ETCS are not a lot different, while underlying movement authority signalling principles are the same - it is the hardware and applications software higher up the layers and method of track to train communication that differ.
Further, Vic line (and Metronet inspired 4LM scheme) DTG-R utilises track circuits for train detection and protection; the other systems do not. For intense headway metro, you need a lot of close spaced short track circuits. The Victoria line is a simple self contained shuttle - DTG-R works there on what is a simple railway. But that Vic line upgrade was specified eon ago - DTG using track circuits is obsolete techonology, no-one would do it now. And. Track circuits are maintenance intensive and significant points of failure. So why would you replace legacy track circuits on the the surface lines with a system dependant on a significantly larger amount of track circuits.