In 2015 i wrote about multiview and API function:

I create multiview with background picture and send it to programm. With shortcut i create SetMultiViewOverlay to change input in multiview overlays.
Or in script - - API.Function("SetMultiViewOverlay","2","2,3") - in multiview input (№2) i change overlay №2 to input №3
Or in script - - API.Function("SetMultiViewOverlay","2","2,1") - in multiview input (№2) i change overlay №2 to input №1
But if in this inputs i have videos - thay don't started, auto audio mixed and other (as checked in "general" option on this inputs)

I think that behavior - autoplay on transition, pause on transition, automix audio and other options in "general" tabs in input - must be work in all cases (overlay transitions, multiview changes and etc.)

And second request(?) - create API access (from scripts or shortcuts) to all (or main) properties of objects (inputs, multiview, overlays), as example - positions (SetPanX, SetPanY, SetZoom - is exist, but only for inputs). It is will possibility to create small animations- as example:
1. Set backround pics input to program (multiview input (№2))
2. Create trigger "OnTransitionIn" to start script.
3. Create script with some actions:
a) SetMultiviewOverlay("2","2").PanX=-2 - hide overlay2 from screen
b) SetMultiveiwOverlay ("2","2","3") - set overlay2 to input3 (simple LOGO)
c) for i=-2 to i=-0,5 step 0,25 begin
SetMultiviewOverlay("2","2").PanX=i - scroll overlay2
end
d) Delay (2000ms)
e) SetMultiviewOverlay("2","2","") - set overlay2 to blank

And we have "simple" scrolled LOGO from left , staying on screen 2sec and switch off

For first part: i dont understand "clone the shortcut" may be it assume - "clone multiview input as virtual inputs" with different sources of multiview overlays ?

For second part: scripting may be interested as engine to create simple animations without xaml, "AfterEffect" and etc.

Small example - simple "Flying overlay in square"
it work with "preview" - send to preview needed input - you see animations and set this input to overlayX(with needed size)

Small video for second example - small-video

About first case - i understand idea with multiple actions, but - it will require more keys - i set shortcut1 to change multiview overlay source to inputX, and set shortcut2 to start video in inputX, and add in shortcut1 trigger to shortcut2. But - i think it workaround. If all checkboxes in "general" tabs on inputs propertiew works always when input sending to program output (direct transitions, overlay, multiview) - this workaround don't needed.