I see what you mean, the fact it returns all hashrates in Mh/s regardless of using scrypt limits the precision I can get. I have to then take the number I receive and multiply it by 1000 to display the correct Kh/s. That is something that would need to be changed in CGMiner. I don't want to try to maintain a branch of that if I make changes to it (because I believe it is still being actively developed), but you can request the change with the CGMiner developer. It doesn't have to send the hashrate in Kh/s... it could just send more numbers after the decimal.