Untangling Rayon and Tokio

Good read.

I already knew about the importance of keeping CPU-bound threads on their own pool, separate from Tokio, and using tokio::sync::oneshot to await them, but I haven't yet used Tokio and Rayon under these load conditions, so I hadn't realized how important it was to not let the two thread pools stay on their defaults when coexisting.