You talk about interactions. In my mind the useful part is the added information density which comes easy (we are good at judging object sizes visually, not by numbers). I also want this information before interacting with the files. The value is knowing in advance, at a glance, what you're dealing with.

When you mention CoG, spinning etc. it becomes game-like — not something I would want in a productivity focused interface. But if you're developing a game or a toy experiment, go for it.

Thats the micro interaction that needs to be explored with iteration. The taptic engine pressure response (IMO) is not the best , but applying some heuristic ux designs I think we can approximate CoG and inertia.