When tracking scanner thread CPU time, Impala simply uses the wall clock time from thread start to finish. it doesn't eliminate the waiting time. so the TotalCpuTime is much higher than scanner actually use.
The plan fragment execution CPU time might have similar issue. although it does eliminate disk IO and network transmit time, it might include waiting time for downstream fragments.