While the development team is thinking about this feature request, please also have them think about the content maintenance aspect of this. If you are copying a block because you want repurpose and tweak, then Copy is great - the original and the copy have lives of their own and there is no ongoing relationship.
HOWEVER, another really important use case is if you have the same block that is used in multiple courses, and if you update the original block, you want all its instances in other courses updated as well. This is a content management use case, and solving it would save subscribers lots of pain and time. Since you have a team structure, seems like you could create a team block repository for reusable blocks and when you reuse a block, you have the option to make a copy and modify, or make a copy and have that copy be updated when the original block is updated.