The problem is that localization is managed by DNN and one of its providers. One way could be by modifying the friendly url provider and create a new one that merges with dslocalizator. It needs investigation, and maybe a lot of time

My hack only modifies the already loaded tab data from dnn.

I have some news: I make some optimizations to DSLocalizator by using cache, there is an improvement of 50% talking about time of localization being applied.

I suggest to wait until next month to see if core comes with some news about content localization implementation.