In the last episode (Mar 27), Mirar @ Pike developers forum said:
While Pike is doing something that might be taking some time, it can run other Pike-threads in the foreground. This is done in a lot of operations, all of those you mention, I believe - all that make sense.
So if you are doing a lot of image operations, it will use several real threads for the operations.
Any place in C code that you see THREADS_ALLOW / THREADS_DISALLOW pairs, that's where the code has released the main pike interpreter lock, allowing other threads to run.