You are correct there is no reason in this case to use an EnvironmentObject. Apple even encourages to make no excessive use of EnvironmentObjects.
Nevertheless an EnvironmentObject can be great too, if you use an object in many views, because then you don’t have to pass it from View A to B, from B to C and so on.
Often you find yourself in a situation where even @State and @Binding will be enough to share and update data in a view and between two views.