Sorry, I'm not sure I understand the issue. Is it the fact that new extents are being added to the production database, and so its structure no longer matches the current structure file in your dev environment?
If so, one option is to restore your database without a structure file. Then prorest will just give you one variable extent per storage area, instead of all the individual fixed and variable extents you have in the prod database. In dev I would imagine you just care about having the correct data and schema, as opposed to the correct structure which might be more relevant in a performance-testing environment.
Note that this approach will give you extents that are larger than those in prod, so if the prod extents are at or near 2 GB you need to ensure that the dev environment has an Enterprise RDBMS license and the prod database you are restoring has large file support enabled.
Alternatively, if the paths are the same on both boxes (or if you have a relative-path structure) you could also just copy over the production structure file along with the backup, and restore with that.