These kinds of things can be tough to assess, at a distance, without actually diving into the CSS code. One way to debug this is to use a customized CSS file that loads after the Mezzanine and Bootstrap CSS files. Changing the Bootstrap CSS directly won't always yield the results you desire, as various parts of the Bootstrap code are interconnected (through cascading) in ways that can be hard to track. Generally, you will be better off copying the CSS that applies to a given element, creating a new set of rules for that element in your custom CSS file, and hacking away on your own code. If this is an element issue (such CSS applied to a div), it should be fairly easy to find. If it's a cascade issue, it can be messy. (Use, with caution, temporarily, and only as a last resort, the !important flag to make sure that your rules are loaded and not Bootstrap's).
Also, Bootstrap's use of background-image is discussed in threads
like this one, which explores both options (changing Bootstrap, and creating custom css).
Also, background-color will always lie behind background-image. (The spec is
here.) So, this suggests that one line of action might first be to remove background-image properties to get a look at what's behind everything. Then you can selectively add things back in.
In the case of Bootstrap, most of the background-image rules do not actually load images but rather specify gradients, which will override any previously-declared background images (more
here). So, these various interactions can be quite complex. Start with what you can see when you take almost everything out, and go from there.