Lol.
The workaround is "self-developed", simple but effective - based on what I'd like to call common sense - hence, not a secret. So, no tutorial. Well, until now and here:
You create several carousel modules, completely identical except for "Number of columns", "Number of items", and - of course - "Product per slide", most likely depending on how you set up static product listings, to match their behaviour regarding breakpoints in your responsive template.
To use the sample site you linked to, say 4 columns for large screens, 3 columns for tablets, 2 columns for small screens. Perhaps also a single column for phones?
You publish all these modules to the same template position, or alternatively, load them into the component area or a Custom HTML module with "loadposition" or similar. The important part is that you give them individual classes, either module classes (in case they are all individual modules), or by wrapping them into individual divs (in case you use "loadposition" or so).
Now, all you need to do is write some custom CSS with media queries where at your usual breakpoints the good class gets a "display: inherit;" and all others a "display: none;".
If your template framework or what they call it provides you with ready-to-use responsive classes for certain screen sizes or the individual breakpoints, it's even easier as you can use those as module classes, or the divs, whichever is applicable.
Indeed, the appearance is then almost the same as on your sample link. Again, it's not responsive but "adaptive": depending on screen size, you get to see 4 or 3 or 2, or maybe even only one column per slide. Needless to say, of course you can also configure it to have multiple rows or not, e.g. (columns x row) 4x1 on large screens, 3x1 on tablets, 2x2 on small screens, 1x2 on phones. Etc etc etc.
Hope it helps. And maybe not only you, but also some others who were too busy with other stuff to think of this. 
And then it might be soon all obsolete... once the HikaShop devs turn the good old plan of making the carousel module responsive into reality.
Last notes:
If you have difficulties visualizing what it looks like, I could PM you a link to a client site I built.
Also, I found it easier than setting up a 3rd-party module I tried (which works, but whoever designed the backend must be from the dark side of the moon, so I won't name it here). And it's "lighter" on the website then loading yet another extension, risking JS conflicts, and that kinda thing.