The Erlang VM can intercede into a running process, and also does this with some of it's BIFs implemented in C.
From what I know, they cannot, not at arbitrary places, and that's why the scheduler is a cooperative one.
From the Erlang docs on process priority.
The BEAM VM can kill, halt, or suspend a running process at anytime from outside the process. It does not need to wait around for the process to exceed its reduction count limit.
Some of this capability is even exposed to user-land applications. The exit/2 function builds on top of this capability when sending in th atom 'kill' as the second argument. As do the suspend_process/1, suspend_process/2, and resume_process/1 functions.
The reduction count system is just there as a kind of fair-scheduling determinism semantic. Exhausting reduction allocations is not the only way the VM has to interact with running processes.
> From the Erlang docs on process priority.
Well, apparently you're right. I must take back what I said about Erlang scheduler.