Some counterpoints:
1. Micro-lambdas
How many routes does your application have 3, 30? Trying to maintain 30 different codebases and deployments would be a nightmare.
Package size.
Package size is unlikely to be much different by adding a little extra code, especially if the code for each route uses the same set of libraries(which will make up the bulk of the package size).
Least privilege.
If it makes sense to limit a routes privileges, you can simply deploy the same lambda code separately, with a different role.
Upgrading.
On the contrary, upgrading a lambda that uses a single codebase, is much simpler than having to deploy multiple systems and deal with the issues of interoperability and compatibility between versions.
Reusing code.
Also much much simpler with a monolithic codebase, the code is right there, ready to use.
Testing.
Testing a monolithic app is very straight-forward, you don't need to setup a complex integration test environment, all the functionality can be tested locally.
4. Lambdas calling lambas
I tend to agree with this one, at least for synchronous calls, but you can also call another lambda asynchronously, actually this is something you tend to find yourself doing if you go down the path of breaking down a monolithic lambda.
5. Synchronous waiting.
Yes, from a cost perspective, you should minimize the amount of time your lambda is spending waiting on external IO. However, from an application complexity perspective, you should make things as simple as possible, building overly complex event based lambda flows, can make it really difficult to debug and maintain your application.