I might pick a nicer phrasing for your last point: if your team is not good at clean architecture (separation of concerns, conceptual model, etc.), microservices will “solve” that in the same way that adding gasoline solves a fire. If your team has gotten better at that, however, it might be a good strategy for migrating pieces out of an old system.