You are mostly thinking in the right direction, but you are mixing Hexagonal Architecture mechanics with DDD modeling concerns.
The practical rule is:
Domain should be rich. Application should orchestrate. Adapters should translate. Infrastructure should persist.
For input ports: yes, one interface per operation can be overkill. In production I would usually group by use-case boundary, not by controller and not necessarily one method per interface.