Hi, definitely interesting. I looked into the Jobs system briefly and it seems like a lot of others encounter the difficulty of trying to use Jobs without copying large amounts of static data between jobs and the main thread. It seems like Unity Jobs is a lot more "managed" in this way. Some people suggest using native multi-threading instead, like C# async/await, which are more flexible with concurrent data access and should be safe if your threads only need access to read-only data.
That said, you've got one of the most interesting evo sim projects going right now and I'm pretty excited to see where it goes. I even got to teach my gf about neural nets because it happened to be on screen at the time. crazy