Answer
Generally no — a workflow only reacts to an incoming OData call, so it can only influence what happens if that specific dropdown selection itself triggers its own OData call whose response the client framework then uses to populate the target field's data. If the dropdown's selection doesn't trigger a separate OData call that the client consumes for that other field, there's no hook for a workflow to intervene before Save; this isn't something workflows can generally do purely client-side.