Hello @millpreet , I'm a Laravel (10+ years) and Twill (3 years) developer, that did a single Drupal website 1,5 years ago.
What I found doing Drupal is that, if you just need to build a website and your work would be mostly on frontend, it can be very easy, maybe easier than Twill, but if you need to do custom backend stuff, interact with external services or APIs, you need to know very well Drupal inner-workings. As soon as you need to change a simple query to do what you want, things get very complex on Drupal, while on Twill you have access to your Models, you can query them easily and just do what you want.
On Drupal you need to be also fluent in hooks, in order to inject your custom (and very simple) stuff on it, and hooks are hard to "get".
On Twill you won't have access to many ready-to-use modules, but this also means that you are free to use anything available for PHP or Laravel very easily, it doesn't get on your way. If it's not something you need from Twill's CMS dashboard, you just install a package, create your routes, controllers, models and service classes, and you are good to go. If it's something you need to integrate on the CMS, you just edit a Twill controller, repository or model and it's done, you have access to them all.
On Drupal I had to go over a bunch of steps and hire a contractor that said to me a bunch of time, "oh, yeah, you need to create a module do to this..." or "oh, no, this is not the right hook, you needed to use this other one" or "wait, I believe this module has to be patched to work on 8, I have the patch right here if you want to apply".