Replace your check boxes with buttons that run a script to a) check to see if that value is already in a set of related records and b) either adds a record (if value does not exist) or deletes the record if it does. Hide Object When settings or a conditional format can enable the button to change appearance just like a check box would to continue the simulated check box behavior.
Perhaps a picture would better explain the form
Lots of options (checkboxes) the user can select many or no values. Each tab has a field with many checkboxes. How do I separate/create a new record for each checked value, when multiple values can be checked. As well since this data is collected in the remotely in off-grid places a UUID is create for each record, will this limit my options for creating individual records for many checked values? Or should I allow UUID duplication?
Do you really need separate records? Could you just store the multiple values into a single field in 1 record? What are you doing with the records that requires multiple records?
With that said, you could just loop through the checked values, putting them into a global key field that controls a relationship to the related records' table or table-occurrence, and either create/edit/delete the related record (depending on what you want to achieve).
What I described still works. You might set up some portals to a table of all the check box values as part of your interface design. This can enable you to set up exactly one button in a portal row of each portal that looks and acts like a check box while generating/deleting separate records in a related table.
Separate records, BTW, allows Travis Heckford to do analysis and tabulation of the values selected not easily done when the data is stored in a conventional check box, such as calculating what percentage of these records has "alpine anenome" selected.