Why touch the abstracted method/function when it's perfectly being used by other parts of the code? If there is a new requirement that will need you to change

Why touch the abstracted method/function when it's perfectly being used by other parts of the code? If there is a new requirement that will need you to change this method/function, that means that you need to copy it and make sure you name it to easily document whatever this new requirement is. Now if this abstracted method/function has a lot of code that you don't want to be duplicated, then you might wanna refactor it with SRP as your guidance. In addition to SRP, side-effect free methods/function will greatly help. I hope I made sense here.