I fully agree with Jon, copy&modify should not be the first choice, rather the last one. The more copies exist the more work it becomes to fix bugs, improve the base functionality. it, etc. Maintainability goes down.
The example looks exactly like a use case for subclassing in the OO-world, or, if there is no OO available as a case of modularization and configuration.
