One option may be to assign you work at a higher level and have the product manager define stories/epics with corresponding acceptance criteria to be met at the end of the sprint. That would remove a lot of the sub-task explosion and provide you some freedom to decide how to write the code in order to satisfy the acceptance criteria.

Kanban is a bit more flexible than Scrum, as devs aren't locked into a specific set of tasks for each sprint but the micro-management with cards still exists.

In my experience, teams are more productive when they spend time on design discussions (and not card creation.) I consider standups completely useless.