Thats not the way how scene7 works. You do not have to create scene7 preset for every image but only a finite number.
When you upload an image in AEM DAM then AEM create renditions of that image based on the pre configured sizes in the Update Asset workflow. For example if you created two renditions of an image - one with 150X150 (for thumbnail) and one with 600X600 (for detail page). If you use that image in a listing component to show thumbnail then in your component you will code the URL to get the thumbnail rendition and in the carousel component you will code to get the 600X600 rendition URL. This allows you to reuse the same image in two different contexts. However, the DAM workflow can create only static or one time renditions and does not allow you to fetch on the fly renditions like Scene7.
Obviously you can upload two different images with two different resolutions but then you are unnecessary uploading duplicate images and not reusing them in multiple contexts leveraging the benefits of scene7. With this you are adding more work for your creative team by asking them to create unnecessary multiple versions/renditions of the same image which you then upload to DAM.
Similarly in Scene7 for every rendering context of an image you will define a preset (ex. thumbnail, carousel, hero) and then in your code you render the image based on the context or based on user input (For example in image component a user can choose the preset). You are not creating preset for every image but rather creating a preset for various sections of your site where you are showing images. You can reuse presets across multiple components and pages where the same dimension and quality of image rendering is required.