The clipboard functionality exists but you'll require a plug-in for newer browsers. (this will need installing on each machine your accessing tm1web/workspace from
https://www.ibm.com/support/pages/plugi ... te-tm1-web
My advice would be to stick with the out-of-the-box tools, tm1web/paw/pax for a user interface. If only to ensure the interface you've worked hard to build remains supported and successors can pick up the toolset. Planning Analytics is still a relatively niche job market, so if you venture from the main tools, models could fall into disrepair once your gone, as successors may not have the knowledge to support it.
I would steer clear of going overboard with VBA as they can be hard to maintain/update and rollout. By all means you can have some vba code to help with tasks, but I wouldn't rely on it as the primary interface for users.
Rest api, there is a large learning curve, and to develop an website/interface that api will take considerable time.
Regarding rely speed/interaction there are many factors that can affect performance, such as volume of data, calculation times and network speed...
I would also say excel itself is not prone to performance problems which can get unwieldy when they get too large or have too many links/lookups
Also try to avoid mass data dumps, teach users to interact with slices of the cube, rather than them exporting everything to excel as this will cripple the system and hinders security of data.
It sounds like you're users love excel, so maybe start with Pax to get them on board. If users need to contribute data, then you could try using explorations. If you know how to write a view on mdx you could also define exactly what data you wish to retrieve and no formulae are needed so users can paste merrily.
With Tm1web there are also various config settings which can enhance the user experience, such as choosing when to recalculate and picklist work very nicely to control user inputs