Font metadata is a bit of a mess (even with system fonts you'd expect to behave "correctly") and typst has had issues with it before (see e.g. https://github.com/typst/typst/issues/576). If following the fix in https://github.com/typst/typst/issues/4493 doesn't work for you, then most likely this is an issue with the font and not with typst per se; unfortunately the least-effort workaround then is to patch the font manually with e.g. fonttools or FontForge.