performance – Should one call Insert/Update/Delete DAO 2nd threads “before” OR “in” onActivityResult


I understand that query of databases is done on a second thread and not on the main thread.
But where should one trigger the Insert/Update/Delete “RoomDatabase.databaseWriteExecutor” calls when it comes to large user application form in general, on the DisplayActivity in onActivityResult or on UserFormActivity after pressing the Button?

I understand that AndroidX Room with a View – Java says do it on onActivityResult of caller Activty?

Route 1 in pseudocode for Java: do it in the onActivityResult of caller DisplayActivity:

1. Enter: DisplayActivity
2. Click: Button Go to Form
3. Enter: UserFormActivity with Intent Bundel
4. Fill in: Form with Fields ['note','color','country',...]
5. Click: Save Form
6. App: Check Form Return to DisplayActivity with Parcelable Bundle  
7. Enter: DisplayActivity
8. Trigger: onActivityResult 
9. App: Insert/Update/Delete Data to SQLITE
10. View is updated.

But wouldn’t it be better to do it on the activity dealing with the form?

Route 2 in pseudocode for Java: do it in the OnClick of UserFormActivity

1. Enter: DisplayActivity
2. Click: Button Go to Form
3. Enter: UserFormActivity with Intent Bundel
4. Fill in: Form with Fields ['note','color','country',...]
5. Click: Save Form Button
6. App: Check Form Return 
7. App: Insert/Update/Delete Data to SQLITE 
8. App: Return to DisplayActivity with Status
9. Enter: DisplayActivity
10. Trigger: onActivityResult adjust view depending on Status return Bundle
11. View is updated.