I can understand the need at some level.
But DI Studio is all about metadata, not "actual data".
AFAIK there is no standard functionality that you can perform to make this happen linked to check-out/check-in.
Also consider data in external datasets.
So the question is, how big of problem is this? Maybe it can be solved via communication in the development teams?
Also, locking down tables may halt other developers/testers that need to recreate the table for their job.
What I can think of is that you create OS script to change authorizations for checked out scripts. But who will execute that?
Data never sleeps