What I try to do in most cases, is to find concepts in the domain that combine several properties. Then I create value objects that represent these properties. The result is that only a single object (A value object) is passed around.
A very typical example is “address”. Instead of passing around “street”, “housenumber”, etc, there is only a single object.
Yes, your solution is going to help to some extent.
But some entities have lots of properties by nature, for instance a
Customer entity in CRM system & maintaining those properties & their
commands, DTOs, JPA classes etc are no fun, moreover for some command
(update, approve, etc) you only need just a few of them.