Can you elaborate, as someone with little AWS experience? Are OIDC based creds just more scoped? What makes them special?
Even if the attacker had access to env vars from running jobs (which includes the signed token needed to do an OIDC role assumption), those tokens have a short expiry time, and even if an attacker stole that token and performed a role assumption then that session can only be valid for a maximum of 12 hours in AWS, and then you know the attacker is out of your account.
It just significantly reduces, practically nullifies, anything that an attacker can do in your AWS account.
A session token with only a few minutes validity can be enough for someone to make their access permanent.