It might be possible:
1. If you store the the recurrence for fields that you want to be expanded automatically in field1 and use DataRecurrenceField="field1".
2. The recurrence for fields that you expand manually must be stored in a different field, e.g. field2.
I'm sorry but we have gone far from what is a supported scenario. I might be able to give hints on how to approach certain problems I'm not able to provide the complete solution.
And that the hints are just that - hints on where to start. The recurrence is not trivial and as you progress deeper and deeper you hit harder and harder problems.
So asking "is xy possible" is a tricky question. In some cases the answer is yes, it is possible. But that is different from "it is a good idea" or "it is easy".
Even the built-in recurrence is not an easy setup (if you decide to support exceptions from the recurrence rules). The recurrence support is designed for this scenario - it brings some compromises in order to make it easier.
Switching to manual handling exposes these limits. So at this point it's good to ask whether to stay with the DayPilot recurrence support or whether to choose another solution for defining the rules and expanding the occurrences. With manual expanding you are not bound to using the built-in support and you can replace it with any other implementation.
And the next step, adding mixed support for both the built-in recurrence and manually handled recurrence complicates that even more - and you need to evaluate your architecture from that point of view. It is possible that it will handle it but it might not be the case.
So I apologize for not being supportive but we have drifted into area which I'm not able to back.