If you have the ability to define the number of rows that will be allowed to be input into the repeat section, what you can do is create 1 destination per row. The main "gotcha" when doing this is that Sharepoint Lists depend on a Unique ID to determine if it will be updating an existing row or creating a new one. When dealing with a repeat, your Unique ID needs to be something that is unique per row of that repeat, otherwise it will just overwrite the previous.
For example, if you have a repeat section gathering an employee name and a date for timekeeping, use a String Concatenation question to combine those 2 data points so that you will have unique data per row (like "Ian Chamberlain - 09-27-2021") and use this CONCAT question as your Unique ID because it will then see that each row is different than the last which will create a new row in Lists. The Name and Date will not work in every situation, sometimes you can use an Asset number or something else, but a Date is always good to include in the Unique ID. You can also you more than 2 questions to come up with the Unique ID.
Once you have figured out your Unique ID, you will need to define the number of Rows that will be allowed to go into the repeat. Limit the number of rows in your repeat section to what you have defined. In each one of your destinations, you will need to specify which row that destination will be for using DREL. %a[QuestionLabel] would refer to the answer to "QuestionLabel" in the first row of repeat. replacing the 0 with the next number will indicate the next row and so on.
Using this, you can write each row of the repeat to its own row in your List. Your first destination will reference all the questions in the first row with , the second destination will use  and keep on adding destinations until you have them all. Now when your form has multiple repeats all needing to be on their own row, managing that many destinations might become a little bit more complicated.
I hope that this works in your workflow! Let me know if you have any questions.