This hasn't gotten ANY attention for over 4 months!  It looks like Log4J 2 doesn't have this issue at all, so it looks like it's worth switching frameworks.  Its MapMessage does what I need, and JSON is directly supported rather than separate in logstash.