Yes, I agree with your assessment. This is still a bug.

But just to manage expectations: since the workaround is straightforward and it seems this bug is hit fairly rarely, it is unlikely that it will be fixed very soon.