Maybe I wrong and other communinty member correct me but it depends on the instumnetation type. I have expereince with calssicfullstack becasue I always use this instrumentation type. I think in this case port 443 would be enough between Kubernetes range and DT managed (hosts or range). In classicfullstack instrumentation you can deploy a containered activegate. This AG should communicate with the DT managed servers (not the individual host agents with DT managed servers).
I think open fw for worker nodes are enough. Restric the active gate to the worker nodes, in this case containerized AG can connect to managed nodes and connect the cluster api interface.