I looked at first benchmark (funkuch-redux) where C# significantly beats Go (8.3 vs 32).
It turns out that the winning C# programs uses SSE2 intrinsics.
The second best C# programs virtually ties with Go implementation, which is not a surprise: those are pretty straightforward, calculation heavy programs. Easy to optimize so both .NET JIT and Go compiler do similarly good job generating code.
So all we've learned that using SSE2 can significantly speed up certain kinds of code but it has nothing to do with C# vs. Go.
Arguably SSE2 intrinsics are actually part of C#. Apparently they were added as a library in .net core 3 (in 2019?).
You will typically not use intrinsics in your code because a) you don't need them b) they're pain to use
And I could write a Go version that uses intrinsics and it would be equally fast.
The same applies to n-body and spectral-norm at which point I've lost interest in those benchmark because all they show is that someone spent extraordinary amount of time optimizing C# code with intrinsics while the same effort wasn't applied to Go programs.
But by constructions you average Go program will be faster that your average .NET JITted program.
JIT has constant overhead and can't spend as much time generating best machine code as offline Go compiler.
Plus .NET is more memory hungry (.NET object have memory overhead not present in Go structs), UTF-16 strings take up ~2x more spaces than Go's byte strings etc.
Doesn't mean every Go program will be faster than equivalent C# program but it's more 80% in favor of Go.