Hi there Levey,
Unfortunately it looks like that was an old, outdated version of the support article and the information you’ve received in tickets is correct in that this is not something Customer Support will assist with directly.
The article should be updating soon, but you can also find the up-to-date version here:
As such the only option for this to be resolved would be for developers to go back and fix the original bug, which seems unlikely given that, as you pointed out, it’s been around for quite some time already.
Sorry for the bad news!