I don’t know if this answers your question directly: but the article points out that this is a module, not a primitive that’s in the kernel itself.

The idea here is that wine/proton can interact with this module directly if it’s loaded, or continue to use their wrappers around existing fsync if not.

I expect that means a little less scrutiny since if it segs the user can choose to not load it and achieve a stable OS.