Scrum master here (amongst other things). Just want to point out that nothing mentioned in your comment is "Scrum". Though they can certainly be characteristics of terrible attempts at implementations of scrum and other methodologies.

The first thing to do when considering scrum is really understanding the problem to be fixed or process to be potentially improved and if the best approach is an Agile methodology (Not just Scrum, it isn't the only thing out there and isn't always the best solution). Then only adding as much as you need.

Scrum really shouldn't be adding any bureaucracy. Not any more than a sufficiently complex project would already have inherently. In fact just the opposite, it should cut down on bureaucracy and make teams more (drumroll) agile. Which is the whole point of self-managing teams.

Sounds like this guy did a hacky job while calling it Scrum, and was not at all the right hire for your situation.