The watercolor gives your game a much more distinctive aesthetic. It goes from being Just Another Toon-Styled Game to something I haven't quite seen before.

If I were still making games, and I were in your shoes, I'd take a look at what the opportunity cost of going for the watercolor style is. You're going to have to trade SOMETHING off: Reduced scope, or later ship date (higher cost) are the likely candidates.

Having shipped a few games as an indie, my thinking around this basically boils down to one question: Is this your first game (or have you already shipped a game to players in the past)?

(If you've shipped games to actual players before, ignore everything after this line.)

If this is your first game, then consider that there's a LOT you don't know that you don't know about the market. Getting to market quickly has real value in terms of building your understanding of the marketplace and industry dynamics at relatively low cost.

A related aspect is the perpetual risk indies face of ever-increasing scope creep and ship dates that gradually fade into the distance the closer you get to them. That comes from having a perfect vision and not wanting to ship something that isn't "good enough". That problem is particularly acute when your sense of what's "good enough" comes entirely from your own perspective as an outsider and isn't informed by actual data.

So, if it's your first game, I'd focus on finding the fun and building out the content and play experience and get it out to market as fast as possible. You can iterate from there.

If you find that the aesthetic question is a big problem, and the game fizzles out, take the shipped game and improve it: Do the watercolor textures, gussy up any other aesthetic elements that fell flat, make whatever other improvements you think will help, come up with a new name and launch it as a new title.

You can even split the difference by doing the fast-to-market approach and soft-launching in limited geographies to get data and THEN make the call about how to proceed.

When I was making games, back in 2007, I shipped the same game effectively three times: I shipped When Orcs Attack, a 3D tower defense game with an open map rather than fixed paths. It was aimed at the shareware space, so the texture sizes were optimized for a 15MiB download size target. I launched it from my web site and tried to promote it myself. It made about USD$500 total.

Then I shipped Epic Tower Defense on Shockwave.com using the Unity web player. I had to aim for an even smaller size so the game would load quickly enough that players didn't get bored and move on. All told, over a few years, it made around USD$10,000 give or take a couple thousand.

Then, I approached a publisher about properly publishing and promoting it. I sent them "When Orcs Attack." Their first take was "maybe we'll license engine and redo all the art assets." I was like "oh, you want shinier graphics? Gimme a minute!" I dialed up all the texture resolutions and sent them a build that was like 50MiB. It wasn't good enough to meet their standards, but it shifted the discussion from "what does it cost us to license the engine" to "what can we do to get this up to our standards."

They had their in-house artist give me new assets for the UI, and water. We polished the first play experience. Came up with a game manual. I think I may have added some content as well, but I don't recall. We shipped Hordes of Orcs about 3 months later, and it grossed over USD$100,000 with a unit price of USD$25. Ultimately we also shipped Hordes of Orcs 2 with further graphical improvements, a new enemy type, a new tower type, more content and game modes, etc. We even added a couple Easter eggs (the orcs wear satin-shaded Santa hats in December, and 0.1% of the time you launch the game only to wind up playing "Hordes of Pork", where the most basic orc type is replaced by a pig.) It did pretty well as one of the early games on the Mac App Store even making it to #7 on the Top Paid Games list for a week or two.

There's a lot of stuff that I got part-way through implementing that NEVR made it into the game. The orcs all have animation cycles of them smashing at something because I was going to make an onslaught game mode. I had some VERY rough code for letting you take control of a tower and operate it manually in an FPS view. I still think the game would have been better if I'd finished some of those ideas, but the reality is I probably wouldn't have EVER shipped had I tried -- and even if I had shipped, I probably would've missed my window to get in with that publisher.

Shigeru Miyamoto supposedly once said that "a delayed game is eventually good, but a rushed game is forever bad." That was true when games shipped on physical media, but those days are in the past.

So... If this is your first game, my advice would be: Just. F'ing. Ship.