@max, so that's only when trying to stop CP on Linux? Does it happen on pool switches? And just to be sure, it's Phoenix having high CPU usage, not CP itself, right?

As for the slow updating, can you post a sample of Phoenix output without CherryPicking, a screenshot or copy-pasted text will do, including the Phoenix live info display? Which version are you using exactly?
The slow live stats updating may be happening because your version of Phoenix may be outputting different text compared to what I used while developing, that's why I need to see what its output is. As always, as long as pool switching works for you and you have normal load on your GPUs, the slow stats update may be just a 'cosmetic' problem.

@blacbe, that's a nice increase. While testing I can't say I've noticed any hash rate difference on my GPUs, but it's good to hear you're getting significantly better results.
Any problems with Phoenix so far, serious or no? Are you on Linux or Windows?

LE: As for developing, I've used Phoenix 1.6.2 on Windows and to get it on Linux I did a git clone and used that for testing (this was when I posted the screenshots).