You can theoretically do this entirely through configuration, but your mileage may vary. Conceptually, here's how you might do this:
First, build a custom object with a single date/time field to trigger from, and probably a checkbox to control process builder.
Next, build a Flow that performs a query for the records you want to update, and performs the update. Normal DML and governor limits apply, so if you expect to exceed this limit, you will have to resort to Apex Code. If that happens, you might want to write the entire thing in Apex Code, but practically speaking, you could just execute a batch job from the process builder while retaining the rest of this configuration.
After that, build a process on the custom object that triggers the flow or Apex Code when the box is checked, then creates a new custom object record with the next intended fire time (e.g. 24 hours later).
Finally, build a workflow rule that evaluates when the checkbox is not checked, and has a time-based field update that goes off when the date/time value is reached. The field update should check the box.
Now, you just create a custom object record with the next (initial) start time with the box unchecked. Once the date/time value is reached, the workflow rule will update the checkbox, which kicks off the process, which executes the flow, which will update the opportunities, and then schedule the next execution time.
While this is a pretty interesting mental exercise, an experienced developer could probably write up the initial code in less time than it'd take to point-and-click your way through this design, and without the limitations inherent at every step of the way. The advantage, of course, is that it can be later changed without future deployments.
As an alternative, if you know the records that need to be regenerated daily, you can build a set of two workflow rules. The first rule triggers when a box is not checked, and reevaluates the workflow rules. It has three actions, one of which is to update the field you want to update, and the other is to check the box, and the third is to set a future date/time value. The second rule triggers when a box is checked, and fires 24 hours after the future date/time value specified, unchecks the box, and reevaluates rules. This causes perpetual updates to occur on those records indefinitely. As per the other solution, one initial "touch" is required to kick off the cycle.