Composer 3 managed airflow - Kubernetespodoperator

In Composer 3 we are charged on workers

Web Server: 0.5 vCPU + 2 GB RAM = 2.5 DCUs/hr

Worker (Base): 0.5 vCPU + 2 GB RAM = 2.5 DCUs/hr

if that is the case can we use kubenetespodoperator for the tasks as my understanding is that worker is used only for airflow tasks such as python or bash operator. KPOs run in gke autopilot nodes(completely in google tenant project). does that mean workers are not even used? worker just launch a pod in gke cluster?

or is the worker also depends on KPO and the resource requests we set determines the DCU cost? can someone explain this?