I wonder if you are seeing something similar to what we can reproduce on certain AWS hardware. Our issues were not isolated to specific Erlang versions, however.
https://erlangforums.com/t/pathological-scheduler-behavior-on-specific-aws-instance-types
In particular, we have continued testing different hardware and BEAM configurations with this benchmark.