I can see you've been following the issue on GitHub. The best way to move this forward would be to engage directly with the maintainer through the pull request. Since you've already identified the problem in the PR, here are some suggestions:
Provide a detailed reproduction case - If you haven't already, share the exact steps to reproduce the crash, including your Godot version, operating system, and a minimal example project if possible.
Test the proposed fix - If you're comfortable with it, you could test the PR locally by checking out the branch and building it yourself. Report back on whether it resolves your issue (with or without the problem you identified).
Suggest an alternative solution - Since you've identified an issue with the current PR approach, if you have ideas for how to fix it differently, share them in the PR comments or even submit your own PR if you're able to.
Be patient but persistent - The maintainer Mario was recently on medical leave. If there's been no response after a reasonable time, a polite follow-up comment on the PR reminding about the issue can help keep it on the radar.
Unfortunately, I can't directly influence the development timeline, but your active participation in the PR discussion by providing constructive feedback and testing is valuable and increases the likelihood of getting the issue resolved.
