You are suddenly talking about a mayor release upgrade (3.1 -> 3.2), not an update in the same mayor release (3.2.0 -> 3.2.1). It is well known that there are a few differences between 3.1 and 3.2 extension system.
That's right, they were coded to work with 3.1.x, not 3.2.x.
During the update from 3.2.0 to 3.2.1 you don't touch the extensions folder, that's what I said. So there is no need to re-do your changes you already made to have our 3.1.x-extensions working with 3.2.0
If you found a way to make 3.1 extension work with 3.2, it would be a nice gesture to share the changes with the author or the community
Did you give any hints to the extension developers or the extension team, which extension do not work anymore?