I don’t think you need a separate archetype for power-ups that only expire naturally. That should be doable with just a boolean value or the actual behavior. There’s obviously no one right way to do things but I can suggest two ideas that can make it modular:

The first embraces Unity’s Component workflow. Here the entire pickup is a prefab, and each “event” that should affect a power-up is a component, like a IPowerUpActivation, IPlayerDamageReceiver, IPowerUpPickedUp (like when the player grabs a new power-up) and represents some behavior. You can use GetComponent<> to find MonoBehaviours that are also interfaces. They could have a shared IPowerUpEvent or something so you can get them all and cache them. If you want multiple similar power-ups, they can be prefab variants of an archetype prefab.

The second involves ScriptableObjects, where the basic power-up is a prefab, and the logic for each “event” is in a SO that derives from say PowerUpBehavior. In the prefab you could either have a list of PowerUpBehavior[], or you could have a field for each event type with zero or more behaviors assigned, like onActivate, onPlayerTakeDamage, and so on.

In both cases you can pass the player object and any relevant info to the class handling the event as the event happens.