I would suggest using a different workflow. Make a new form for each visit. That way you have full editor tracking and all that (day, time, who visited, etc) . Plus they can copy over from the last visit make a few changes then submit.
Then have a FC of trap locations. Create a relationship class between the FC and the visit form. Now you can click a point and see all the visits (without dealing with a level down relate).
Then if you really want to get fancy load the trap points in collector with all the base fields. Then launch Survey123 from Collector - using URLs to fill out the header. Now you have a full connected workflow. See this post for more page 7 - https://community.esri.com/groups/survey123/blog/2016/07/30/understanding-survey123s-custom-url-sche...
Just a thought - we changed to this style of one form per visit vs one form for all and there are a lot of advantages.
Hope it helps.