No one has presented a remotely correct fix anywhere on that issue, or elsewhere to my knowledge.

You're welcome to write an actually correct patch for android if you want, one that isn't just commenting out code and probably breaking some spec-compliant bluetooth devices.

Make sure to test your patch against all the bluetooth devices in existence to make sure it doesn't regress.

Do that, make a PR, wait the average third-party-android-PR review time (approximately 5 years), and then if your PR isn't accepted at that point we can maybe say Google is intentionally ignoring this issue.