I’ve figured out a workaround for that - in 4.21, adding any variable with category that you want to reorder (can be even a non-editable boolean variable) into child blueprint allows to control the order of that category inside that child.
That’s not really convenient when having many child classes though, so I hope that this will be fixed in future versions.