@JenMcRuer when you have a lot of points in a Map Tour, the user experience can be very poor. Especially if the part you are relying on is a user navigating the list of points by scrolling. Imagine a user's experience when you have 1000 survey entries listed, and they need to scroll down to find the 721st survey entry. Ugh!
You don't say what your trying to achieve overall in your post in terms of user scenarios, however, I would guess it is not the navigation of the list of 1000 survey entries a Map Tour provides. Rather, perhaps you are interested in the user experience that the map part of a Map Tour provides? Where a user can pan and zoom the map to view data, and can click on points on the map to view more information about specific entry?
If that is the case, and you did mention Dashboards, have you considered using a Dashboard, instead of Map Tour? You could use a Dashboard to provide a similar user experience as that provided by the map part of a Map Tour, and then embed the Dashboard in your StoryMap in place of the Map Tour block (assuming there is more to your story than just the Map Tour.)
For example, create a Dashboard and add a Map and a Detail element, both pointing to your data. Then configure the Map and Layer actions for the Map to (1) drive the Detail element to only appear when a point is selected on the Map, (2) show the selected point's data, and (3) to disable the popup on the Map so you aren't showing duplicate data. Then when a user is exploring your data on your map, they can click on a point to view its details.
Below is a visual example from a student project on tracking balloon debris in the Great Lakes region. A survey with 922 records when it ended. By selecting points on the middle-bottom map a user drives what is displayed on the right: