We hear you and we are trying to reproduce your workaround. There will be solution in the HALion 6.0.10 maintenance update.