delaunator-sharp VS UniTask

Well, the easiest option would probably be to use a different Delaunay/Voronoi library. Delaunator (C# bindings here) should be a pretty good option: it's fast, and there's a good explanation of how to use the data structures it generates. There is some weirdness with how points at the edge of the domain work that you may have to work around, but that will probably be easier than trying to modify another algorithm or write your own. I know I've struggled to implement the algorithms for calculating Voronoi diagrams/Delaunay triangulations, even though I feel like I have a decent high-level understanding of how Fortune's algorithm is supposed to work.

If you click around you see his project links to a JavaScript implementation of delaunay triangulation, which in turn links to a c# implementation: https://github.com/nol1fe/delaunator-sharp

Unless you really want to learn the details of the triangulation algorithm, I recommend to just use a open source implementation in C#. Here's one that works fine with Unity: https://github.com/nol1fe/delaunator-sharp

What I would say, however, is that I much prefer async / await via UniTask over standard Coroutines!

Great comment. The Unity task library is UniTask.

IIRC there's a little more work needed for unity, but Cysharp has you covered (https://github.com/Cysharp/UniTask)

Instead of coroutines, use async/await, combined with UniTask to support Unity's async functions (like scene loading and WebRequests). You get much cleaner code, and proper warnings when not using it properly :)

This is an asynchronous method implemented with UniTask. UniTask is much easier than coroutines to implement asynchronous operations. This method uses synchronous methods of NamedPipe because Unity doesn't implement the asynchronous versions. They don't cause any errors in compilation but result in errors at runtime.