It's a tough question because it depends on a lot of things within your app. Things such as overall UX, UI elements and UI interaction you support today. Is there a wizard teaching your users design patterns of your app (eg. swipe to get to the next step in the wizard for example) and so on...
If you do provide some sort of a wizard (animation perhaps) that teaches your app users to "swipe" the screen in order to go back and forth between the steps, then you could drop support for "tap" interaction.
If such wizard does NOT exist in your app and your usability testing shows a good number of people using both "tap" and "swipe", then this is your answer and you need to support both.
If you do end up supporting both interactions, to Tohster's point, you would need to make sure to place your CTA (call to action) or any other interactive UI elements in each screen of your onboarding/tutorial process flow in a such way so they won't compete with each other and your main content area which supports "swipe" and "tap" interactions.