Can OData provide an optional sync way of serialization?

Discussed with OData Dev, when we (M365) serialize a large dataset, ODataResourceSerializer is very slow (easily take 60+ms for few hundreds of kb at p99). We find that all the serialization methods in ODataResourceSerializer/ODataResourceSetSerializer etc. are async (ex: WriteObjectAsync). However, when the data is ready in memory and huge (in numbers, not the content itself), using async way is a waste (context switch, lots of tasks/state machines created) and is much slower than sync way. Since each async call adds some extra cost, thousands of such async calls add a lot of cost. Actually, I tried to rewrite the WriteObjectAsync to do sync write with OData lib, which is much faster than the ODataResourceSerializer (though still slower than using HttpContext.Response.WriteAsJsonAsync).

Can OData provide an option that we can choose to do sync write? It would help us save cpu/memory as well as reducing latency.