You’re free to create multiple snaps if that fits your needs and there’s already snaps on the store that use this approach, but I wouldn’t discard tracks just because they can’t currently be created on the user side. This sounds like a scenario that would be granted access to tracks and aside from the initial voting period of a week, most tracks thereafter are created pretty rapidly upon request (within hours) if they fit the same cadence, which the PHP versions likely would do. Simplified track request process for snaps with predictable cadence - #4 by roadmr
I think generally speaking people would rather you used tracks if it’s technically possible for you to do so, it neatens the store up and simplifies management. With the parallel installation feature you could even still have the different versions installed side by side. But there are some scenarios where tracks aren’t useful such as content snaps, and the many snaps for many versions approach becomes the only valid option.
Tl;Dr it’s probably worth asking for tracks 