Fair enough... I'd probably stick to Minimal APIs if there were fewer than 5-10 routes in a smaller service. But, with the startup and runtime overhead of .Net, I'm inclined to prefer more monolithic approaches for most general use. Just without weighing it down with a lot of heavy handed enterprisey abstractions.
Edit: Of course, Aspire definitely looks interesting for more complex needs.
They do, and it's not so much about the overhead in terms of performance so much as the cognitive load of spreading out what would otherwise be a smaller/simpler codebase.