Build queue optimizer seems to ignore custom configuration parameter set in trigger(s)?

We have builds that differ only by distinct configuration parameters (e.g. PLATFORM).

The configuration parameter is set in the build customization tab of the trigger.

When two triggers fire, but with distinct configuration parameter, the second build will incorrectly get optimized away from the queue.

The only solution is probably to uncheck “Queued build can be replaced with a more recent queued build”. Unfortunately that implies that multiple builds with the same configuration parameters can pile up.

Is there any solution for this?