Oh no... I had the WR of Minigolf version 0.9.3 in 55s and I think I won't be able to beat it anytime soon, so it's impossible for me to put it?

Sorry, but if we make exceptions then it would set some precedent and future people who did not Live Record or did not provide a Ghost could argue, "hey, but you accepted Xue_Stk'run, why not mine?"...

You could still submit and have the Run rejected, we can put in the Rejection Reason that the Run seems Ok but does not satisfy the Rules, making your Time Unofficial, but others are free to still consider it as perfectly valid, it will just not appear in the Leaderboards here...

There's a bug where the slowdown from an anchor can be canceled out if a speed boost (like a skid or zipper) is triggered on the same frame. This could potentially be exploited in speedruns. I'm not sure how realistic it is, since it has to happen on the exact same frame, but I’ve accidentally triggered it twice while speedrunning. Alayan fixed it in version 1.5, but I was thinking we should maybe add a rule saying runs that use this bug won’t be accepted. Just in case someone submits a WR run racing through bananas ... bug description on github

Personally it is not a big deal, there is no particular reason to ban this specifically Imo, if we do so then why not ban any other Frame Perfect or almost Exploits like the Volcano Island Jump... Of course these Glitches are annoying, but then I think that we should rather have whole Glitch/Glitchless Categories like for Stk Addons than ban specific Glitches, if we decide to ban anything.

And that is, if it were possible to exploit this. I actually performed the Anchor Cancel myself a long time ago while Tasing out of curiosity as I already wondered if we could somehow cancel the penalty, indeed the Boost overwrites it for some reason, but it also turned out that you will still in fact slow down a bit, so I quickly dismissed any possible exploits based on this. Though I guess one would not really notice that in Real Time, especially without a Numeric Speedometer... I just tried again, you lose a few % of your speed for some time, so that is a few 1/100 s loss every s during the few instants after, using a slightly worse path to avoid the Banana will always be better.

Speed Comparison 60 and 120 Ticks after touching the Banana (Top) Vs No Anchor (Bottom, Banana was inactive here, ignore the Anchor at the Left which is a purely graphical quirk of the current Save States implementation), same Inputs. There does not seem to be a way to avoid slowing down, for example using Nitro at a given instant or so.

Nice! I had no idea you'd already looked into this a long time ago. If the bug isn't exploitable, then yeah, no need to add an extra rule. Just from playing, I couldn't really notice the minor slowdown.

If it were exploitable, though, I think a bug in the game mechanics that affects every track should be treated differently than a shortcut like the Volcano jump.