Workflow jobs implementing DLT pipelines seem to work differently than other jobs (notebook, dbt, etc) in terms of parameters...

For notebooks, job parameters are pushed down to the notebook parameters (widgets), overwriting the parameter defaults. A common scenario is persisting the job run ID in a column in the tables for records that are inserted or updated. This is a need I have.

Generally, pushing job parameters to DLT pipelines seems to be a common request (see Can I pass parameters to a Delta Live Table pipeli... - Databricks Community - 30440).

It is confusing and inconsistent that this cannot happen with DLT pipelines, i.e. jobs triggering the pipeline do not push parameters down to the DLT pipeline. 

Are there work arounds?